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:15 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.
5735b681fdb9737f50e033a61e3f48a211340cd18e6e83eb23e1a6704f1f3b01
Both payments are on their chains and locked to the same secret hash 1614d27ab63e22e482d4f8f7d49851e574902f5c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 5735b681fdb9737f50e033a61e3f48a211340cd18e6e83eb23e1a6704f1f3b01
39297ecb432edd6a0327a97859f89b20eb3e9b352790e625bab810ada1219fe5
Both payments are on their chains and locked to the same secret hash 1614d27ab63e22e482d4f8f7d49851e574902f5c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5dc9b4c1189ab8f06e4b6181c4ed95a2556d0c3d9ad51c5596a4520c529a1406
- TakerPaymentSent · TakerPaymentReceived: 39297ecb432edd6a0327a97859f89b20eb3e9b352790e625bab810ada1219fe5
- TakerPaymentSpent: 207f2d69cee2bb194a32b5e53c101deb224666b35441430d99279166f8118391
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.