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:57 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.
cb848fd08f6f95196f065ddcaf7c0b712673efa12bc7713ec8748c94e76bd7a6
Both payments are on their chains and locked to the same secret hash a28d1729670e95b1a358b32f07dc6bda7effb762, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cb848fd08f6f95196f065ddcaf7c0b712673efa12bc7713ec8748c94e76bd7a6
041436e51dca8e11545eac26d28012bfb6ede4f45101bbd8cec42aa47e544a47
Both payments are on their chains and locked to the same secret hash a28d1729670e95b1a358b32f07dc6bda7effb762, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bf1f1b1ec23e9593fc7db22943f35e4acaf1528c04ac832fd67c5658817bedcc
- TakerPaymentSent · TakerPaymentReceived: 041436e51dca8e11545eac26d28012bfb6ede4f45101bbd8cec42aa47e544a47
- TakerPaymentSpent: d01b5e927986a1e19da0e44b0572e0556f5dec38b9a3dfc2dccca6d22f536159
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.