That is in the normal range for LCC/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. 16: mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation)
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 be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch 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 maker can take it back after the timelock. Checked 2026-11-06 05:26:26 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.
8899bcccbe8631278cb5181b9b3aab0a5b1e4ce08b55322b6ed5004d0e0370d4
Both payments are on their chains and locked to the same secret hash 49ecc62a435da0bd8044942f3686ad6fa97f7a94, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8899bcccbe8631278cb5181b9b3aab0a5b1e4ce08b55322b6ed5004d0e0370d4
b389ddac09fec65b16d51bcea94a1a4068f72bb7005941db552aa6f291672350
Both payments are on their chains and locked to the same secret hash 49ecc62a435da0bd8044942f3686ad6fa97f7a94, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 75c7e4ec4c39b8c8b4b3ed99caf0c39ade46eb9e6d9adbc2899e16214046a4fc
- TakerPaymentSent · TakerPaymentReceived: b389ddac09fec65b16d51bcea94a1a4068f72bb7005941db552aa6f291672350
- TakerPaymentSpent: 503984b7b84ff1812d739069354cb5e6738893fc3cdb678b0dec9a09997e9cf3
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 kdf-statsdb-8762.