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 (Signature must be zero for failed CHECK(MULTI)SIG operation) (code 16)
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 still be made for as long as the payment is unspent, and since the timelock has passed the payer can take it back as well, so whichever lands first settles 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 timelock expired 2026-10-28 20:18:34 UTC, so the maker can take it back now. Checked 2026-11-01 03:52:21 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.
901e4af8991a46f62fe94970088468416d423a389143c3ca71e39c47fbfe5d8e
Both payments are on their chains and locked to the same secret hash e47bee366c26a06cd5da1771b37e999fb761e1cb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 901e4af8991a46f62fe94970088468416d423a389143c3ca71e39c47fbfe5d8e
8f7e71f832151fb057e17c57cab25aa61f428881f674e83cdd9dd2e54487ee2a
Both payments are on their chains and locked to the same secret hash e47bee366c26a06cd5da1771b37e999fb761e1cb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3a12818093edfa5e50adff6bd6c0c1bf4be7fbf8b64c80301db7716dbcbab1b3
- TakerPaymentSent · TakerPaymentReceived: 8f7e71f832151fb057e17c57cab25aa61f428881f674e83cdd9dd2e54487ee2a
- TakerPaymentSpent: 537ed4d1a857f27c04521d008f0b902bd053cea7ec55dc3380ab131b8c3a8254
Reported by kdf-statsdb-8762.