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-16 07:34:16 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.
24191ba2116c86201e58b0ebc42f6f933653d51d41105087301aa44e26c013b9
Both payments are on their chains and locked to the same secret hash c8ba1c14c2b36070b03f90b7d5b3a47a994138f1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 24191ba2116c86201e58b0ebc42f6f933653d51d41105087301aa44e26c013b9
de87074b638f529e7b0392acacaf01034f4bd9c710f14c4b992e331ec2c50a0a
Both payments are on their chains and locked to the same secret hash c8ba1c14c2b36070b03f90b7d5b3a47a994138f1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 2ecd8bdc0d32879650f1a57ec88daa9884169c0680a5b8ac2ac54fe65b39ff2a
- TakerPaymentReceived · TakerPaymentSent: de87074b638f529e7b0392acacaf01034f4bd9c710f14c4b992e331ec2c50a0a
- TakerPaymentSpent: 1bad481a4780bcf333ab12f712eee5afaf9a722357a59b00b17c74db2f734feb
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 kdf-statsdb-8762.