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. 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:44:49 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.
339f15d075c928c99bdd66c726b1b28bfe8fd6a71bad88d3a24de0f63091706e
Both payments are on their chains and locked to the same secret hash af5c66672edfc4833630bb426fbcd4ee4d1b9431, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 339f15d075c928c99bdd66c726b1b28bfe8fd6a71bad88d3a24de0f63091706e
7eb2d359c0fc02f8c9d440c3c7b1f53e8f615e9706e14b505fadbf28827882fd
Both payments are on their chains and locked to the same secret hash af5c66672edfc4833630bb426fbcd4ee4d1b9431, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 710b530717a823d622070f47dcbcfc2577db486da281fd572dc8c75c7eacdb0f
- TakerPaymentSent · TakerPaymentReceived: 7eb2d359c0fc02f8c9d440c3c7b1f53e8f615e9706e14b505fadbf28827882fd
- TakerPaymentSpent: 06ec0dd47e467f9e0a4542778e2c19723b5d488c6a3a0cdcac39b83f03873e66
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.