That is in the normal range for PND/LTC. The time a swap takes is set mostly by the block spacing of the two chains involved, so a pair with slow blocks is slow for everyone, every time.
The record stops at MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried for as long as that payment is unspent.
the transaction was rejected by network rules. mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation) (code 16)
By this step both payments were on their chains and the price had been struck, so the trade counts toward the reference price. The claim can still be made for as long as the payment is unspent, and since the timelock has passed the payer can take it back as well, so whichever lands first settles it. Whether it was retried is a question for the chain rather than for this log.
The chain shows the maker's payment still sitting in its contract: neither claimed nor refunded. The maker had already collected the taker's payment by this step, so the taker paid and has not received the maker's coin. The secret is public, so the taker's claim can still be made; the timelock expired 2025-09-21 15:42:26 UTC, so the maker can take it back now. Checked 2026-11-06 05:05:23 UTC. It will be asked again.
Wondering whether this one is yours? SwapScope cannot tell you: the parties are salted hashes, so that nobody can test a key against this data, and that cuts both ways. Search this swap's uuid in your own wallet's swap history, or open the payment transaction above on a block explorer and see whether the address paying into it is one of yours.
a8478e2c2c15b3619e916400416cb82fb9b852695de8464a077885d58267ad59
Both payments are on their chains and locked to the same secret hash 27e97fa8a22ff5d0e923d2e14aca9d234f359dc2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a8478e2c2c15b3619e916400416cb82fb9b852695de8464a077885d58267ad59
93865587ef3d251619225d21b737b6eac8fcc7ca16d56ed2b87e7aa823185397
Both payments are on their chains and locked to the same secret hash 27e97fa8a22ff5d0e923d2e14aca9d234f359dc2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b8c2e01a55f420c08061bbcc9e5df5b110b6f49ee4356ed2302bb16b730f768c
- TakerPaymentSent · TakerPaymentReceived: 93865587ef3d251619225d21b737b6eac8fcc7ca16d56ed2b87e7aa823185397
- TakerPaymentSpent: 7c35699654463c938bfaf7818966060a9c2968e18097511cd3031de072735cd1
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by defistats-gleec.