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. too-long-mempool-chain, too many unconfirmed ancestors [limit: 25]
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 08:03:36 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.
f9810ee2e83e37b3dd7da844ef1abade36b021c5c4d495bd29053f9ebd82746c
Both payments are on their chains and locked to the same secret hash 04947f93c63855c676a2d6e2c202f49119bd977d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f9810ee2e83e37b3dd7da844ef1abade36b021c5c4d495bd29053f9ebd82746c
fcfb821393650b67acc4a75333320015895ca62470f2f77a080ff230ba36d68f
Both payments are on their chains and locked to the same secret hash 04947f93c63855c676a2d6e2c202f49119bd977d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b84d63b6dd116975a85b7bb2c1d542a185474b4d0c3eeb04451177a8c8f17752
- TakerPaymentSent · TakerPaymentReceived: fcfb821393650b67acc4a75333320015895ca62470f2f77a080ff230ba36d68f
- TakerPaymentSpent: d992b86d93c8157885f0b2564cf0126480f9cd2b31e31fb1f8619f7e738e9adb
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.