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:19 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.
7ab85bbc74021812787bd6a2000bfe9b98506e2c54c8fd52f264e574656c21eb
Both payments are on their chains and locked to the same secret hash 8c09ed2a699c55d22f45e82e54539e020e2e4323, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 7ab85bbc74021812787bd6a2000bfe9b98506e2c54c8fd52f264e574656c21eb
436add248f6ad4de84bff1141efc510269610c54dd51ba94932e8dde143a3e81
Both payments are on their chains and locked to the same secret hash 8c09ed2a699c55d22f45e82e54539e020e2e4323, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 206123d954f8e22060c603914a956c4ad3c4ec71ded5f04a41f0d1712b59b195
- TakerPaymentSent · TakerPaymentReceived: 436add248f6ad4de84bff1141efc510269610c54dd51ba94932e8dde143a3e81
- TakerPaymentSpent: 1eddeca5e4cce22bab20ebf0774286e7d2d28cf4a27f17509668603f3539e9aa
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.