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-09-28 13:09:00 UTC, so the maker can take it back now. Checked 2026-11-06 01:34:25 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.
f27e35f3c998c4393f9776fd1e0af045ed360e91a9d951d7fe30269e2b1fb043
Both payments are on their chains and locked to the same secret hash 793c21d5e63c0fbac71b0099a3f134c86728a1ae, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f27e35f3c998c4393f9776fd1e0af045ed360e91a9d951d7fe30269e2b1fb043
6a4dc1f71d97ba6518ce41599ce51001e3d4688e7eccc992cbeec9105a741f99
Both payments are on their chains and locked to the same secret hash 793c21d5e63c0fbac71b0099a3f134c86728a1ae, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 278c77cb4e5a25a872e012e613afb225ff8450ddb8c49c09801fb03e5ea69d60
- TakerPaymentSent · TakerPaymentReceived: 6a4dc1f71d97ba6518ce41599ce51001e3d4688e7eccc992cbeec9105a741f99
- TakerPaymentSpent: 3a7f4dde15a36e1e8e4bf6c277980e7bede113d7e8352327eeb1270aa69d9314
Reported by kdf-statsdb-8762.