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 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:25:03 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.
39cfaf913a61f25638a24132bec0f53294f06950a98672577ff73566c7098734
Both payments are on their chains and locked to the same secret hash 51d4286675d73b8aa678815f80af0e6c38f57bdc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 39cfaf913a61f25638a24132bec0f53294f06950a98672577ff73566c7098734
76eb4e7a3e3ddff050e0d1053d0cb89407fc5366dedbf551d4e4d6f15524ce77
Both payments are on their chains and locked to the same secret hash 51d4286675d73b8aa678815f80af0e6c38f57bdc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 033922a41fbcd41062355186e6866571102616051c61c61d32603bc0795242c3
- TakerPaymentSent · TakerPaymentReceived: 76eb4e7a3e3ddff050e0d1053d0cb89407fc5366dedbf551d4e4d6f15524ce77
- TakerPaymentSpent: 7b07b7d15e306da66dc89ce10f72bb93240dc823fe3c9c613f001b2e6cdfb347
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.