This one took about 26.0× the usual for LCC/LTC. Waiting longer than usual is not in itself a failure: a swap waits on confirmations from both chains, and a slow block or a busy network stretches it.
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: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.
d62130b0dc85475af5f2c03f99de70ce3fdbb10375a190f0e7cfaad388677b32
Both payments are on their chains and locked to the same secret hash a48abb9aefcf37de683e5c920bc97757f3f43851, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: d62130b0dc85475af5f2c03f99de70ce3fdbb10375a190f0e7cfaad388677b32
aa262829ac47bed703e241ae2fd73f8038ecce351ad667f303a4691cb17b3a27
Both payments are on their chains and locked to the same secret hash a48abb9aefcf37de683e5c920bc97757f3f43851, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1d4706bfa53c91cf786cb5274ee87c92009357bfbe8c14a9455e53ab94d023c1
- TakerPaymentSent · TakerPaymentReceived: aa262829ac47bed703e241ae2fd73f8038ecce351ad667f303a4691cb17b3a27
- TakerPaymentSpent: 75c9cf56f8db60b5ff9c184bb60cde89929270508cc6261a4c8b573ba00e47a7
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.