An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
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-27 01:59:43 UTC, so the maker can take it back now. Checked 2026-11-01 03:53:29 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.
6d610ed2163fac94be74a1a5d7bd5b433481d282fc0c4d7992d271ce08c32971
Both payments are on their chains and locked to the same secret hash d4dc5e737df017e6794c2536d83f78e973e3f705, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6d610ed2163fac94be74a1a5d7bd5b433481d282fc0c4d7992d271ce08c32971
9a47b615f4f1ac871f6bb8c413ae5dc2b08372cb12de40dfa41c8cd46ea705de
Both payments are on their chains and locked to the same secret hash d4dc5e737df017e6794c2536d83f78e973e3f705, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 8b2c2729e389311c04aac5cbd9398034a1d7f9613a6a4b3ef60ea211495d66df
- TakerPaymentSent · TakerPaymentReceived: 9a47b615f4f1ac871f6bb8c413ae5dc2b08372cb12de40dfa41c8cd46ea705de
- TakerPaymentSpent: 24ecc2168e8ae0c7e28fc01b95d4f8df29ee6d18a216ab1e8dd9cfabe796dfa1
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.