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.
taker_swap:2010] "eth:3257] request MethodCall(MethodCall { jsonrpc: Some(V2), method: "eth_sendRawTransaction", params: Array([String("0x02f9011001048401d947ce8404d091c38302f9b89461eec68cf64d1b31e41ea713356de2563fb6d3f180b8a402ed292b7ca1b4b378db973c2028a12c542ca327e627dbcb19a448e404d8431ad465e3810…
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-20 13:06:54 UTC, so the maker can take it back now. Checked 2026-11-04 09:13:30 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.
8bc4a6be2109400ed71402bc6cc0007211533cbc05bd8b3d11db90b7ea96d630
Both payments are on their chains and locked to the same secret hash ab59889c3d26c855200edb75bef152093dca68b4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8bc4a6be2109400ed71402bc6cc0007211533cbc05bd8b3d11db90b7ea96d630
c612d7f8f4b28b7a56356e8c516d5bade340c94590f449d40d52a6027d424c32
Both payments are on their chains and locked to the same secret hash ab59889c3d26c855200edb75bef152093dca68b4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 91878d5dff9f61d66d48213f27a9061fdad9f3fb6ed9b7004c1e0a782909d99d
- TakerPaymentSent · TakerPaymentReceived: c612d7f8f4b28b7a56356e8c516d5bade340c94590f449d40d52a6027d424c32
- TakerPaymentSpent: 4b094af5671cd5b1b6dd6f6cfe23e5aa2a34a9ab490007ae99f4140a27417d23
Reported by kdf-statsdb.