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:01 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.
a5de756ae8db43df4f55cd652f91a16213f95929686087ccff0f97790cdfbcf7
Both payments are on their chains and locked to the same secret hash d06afe9b8b7e085a05f0155b68840c5ce1da679e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a5de756ae8db43df4f55cd652f91a16213f95929686087ccff0f97790cdfbcf7
54a0e1a7111b83b55c92e1b69e88d1b9bf62767fbe653132647ff37f09b213f8
Both payments are on their chains and locked to the same secret hash d06afe9b8b7e085a05f0155b68840c5ce1da679e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3bfba28c4a098943995a12b83a9b4dd3a8c4db91c2680cce85e5d1e2ad4edbb9
- TakerPaymentSent · TakerPaymentReceived: 54a0e1a7111b83b55c92e1b69e88d1b9bf62767fbe653132647ff37f09b213f8
- TakerPaymentSpent: 018741cdbcc241d7737de5e2944807bbceec28189cc551aa7319a268475cddae
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.