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:15:40 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.
a50449f8ae79812d1ed8c302c59950ddb8dc2cd058a40cf4c736fc0f00cc5ab6
Both payments are on their chains and locked to the same secret hash e3f136fcc08ef3182f576a5691bcc71b5eb05f4d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a50449f8ae79812d1ed8c302c59950ddb8dc2cd058a40cf4c736fc0f00cc5ab6
b9ebd395494d0856dfd3fd966a3c9e0f3cda492fec840674b1ea7708cc27df07
Both payments are on their chains and locked to the same secret hash e3f136fcc08ef3182f576a5691bcc71b5eb05f4d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6c007c045e4879ca8eea14e473d0d29e14a329c81c3ab1daf4997c32a0964dd6
- TakerPaymentSent · TakerPaymentReceived: b9ebd395494d0856dfd3fd966a3c9e0f3cda492fec840674b1ea7708cc27df07
- TakerPaymentSpent: 5777db1c81bbed19302faefab632ab226dca373c619401833bae5ce09eabf0cf
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.