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:25 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.
ee31815a4ff4f1e5342a37638d73d7ffcc8040674ab32cfb45b023dad059b685
Both payments are on their chains and locked to the same secret hash 8e21e83971e5613a8750101c5ab40f124655c55a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ee31815a4ff4f1e5342a37638d73d7ffcc8040674ab32cfb45b023dad059b685
1d379c4a8c070c4f3ba60549794a22e947956ab9ef4d026385fdf919015e30b6
Both payments are on their chains and locked to the same secret hash 8e21e83971e5613a8750101c5ab40f124655c55a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f53a6839de114d5d590257459317146ff0f5f72e783d118f18c4b0832bed8ce9
- TakerPaymentSent · TakerPaymentReceived: 1d379c4a8c070c4f3ba60549794a22e947956ab9ef4d026385fdf919015e30b6
- TakerPaymentSpent: f446a9b640c4eaa231f319ac59e3e97deecd7f39112406c136cbf5ddfae9cbeb
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.