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 19:33:02 UTC, so the maker can take it back now. Checked 2026-11-01 03:02: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.
a930e209581ff9a5b211aa01b057ff2713c4e6edd125ba2413f447a6171d485f
Both payments are on their chains and locked to the same secret hash 3205cafb2139cef8333d94a99ed0b20a9c19bd8f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a930e209581ff9a5b211aa01b057ff2713c4e6edd125ba2413f447a6171d485f
9f6b15fc74a0b20672e9a4b38e829945b423ff5ff6681a22284481113805272a
Both payments are on their chains and locked to the same secret hash 3205cafb2139cef8333d94a99ed0b20a9c19bd8f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ecdf8a0dadf026402cfad4802309d8999f1e7e53a919dae306c94313b3ee987e
- TakerPaymentSent · TakerPaymentReceived: 9f6b15fc74a0b20672e9a4b38e829945b423ff5ff6681a22284481113805272a
- TakerPaymentSpent: dbaa5a6d24e8c749aa6faf03ba238148923283778a508f464b3d0f3fc079099c
Reported by kdf-statsdb-8762.