This one took about 79.0× the usual for LCC/DGB. 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. 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 still be made for as long as the payment is unspent, and since the timelock has passed the payer can take it back as well, so whichever lands first settles 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 timelock expired 2025-12-10 19:15:38 UTC, so the maker can take it back now. Checked 2026-11-06 04:52:33 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.
75eaa1d3fe9d9298f31d9191171f54b348b951c120a7a6ceea373a230f56c53d
Both payments are on their chains and locked to the same secret hash 169818ae8d5db84e55ece926131d5a2a1e5df9aa, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 75eaa1d3fe9d9298f31d9191171f54b348b951c120a7a6ceea373a230f56c53d
b1687b07e927424346064ac9d98559753db12281080b90b677d8ef6a819b36b2
Both payments are on their chains and locked to the same secret hash 169818ae8d5db84e55ece926131d5a2a1e5df9aa, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9639d03520f5316eaa3a2d150569bc37f02d97c6fe4eb26b3afc2cb087c8f54c
- TakerPaymentSent · TakerPaymentReceived: b1687b07e927424346064ac9d98559753db12281080b90b677d8ef6a819b36b2
- TakerPaymentSpent: fdf05ea7a70d3dbf4328d0d29994fc27acc575a75609b9c3029ba89449d04311
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.