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 TakerPaymentSpendFailed. The maker's claim on the taker's coin was rejected; it can be retried for as long as that payment is unspent.
maker_swap:1172] !taker_coin.send_maker_spends_taker_payment: utxo_common:1682] HTLC spend fee 24933280 is greater than transaction output 10052594
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 taker's payment still sitting in its contract: neither claimed nor refunded. The maker never collected, so the secret was not revealed and the timelock expired 2025-10-22 16:49:19 UTC, so the taker can take it back now. Checked 2026-11-06 05:04:46 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.
f8cabda3092c57971b3941a622c3d7d93447bd93b1a25c8a3e1f879e7c82d8ed
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentReceived · MakerPaymentSent: f8cabda3092c57971b3941a622c3d7d93447bd93b1a25c8a3e1f879e7c82d8ed
- MakerPaymentRefunded: 155af2f8040a88834b864c066da30fb2e9dad8a0936a08944fb51b070b81af65
8fc54e3dab42e82636de61c4812aeca1bf5d3f017f4e8a3f8c631a425e89c9e7
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 6c9fcb3cd0d83c45b5365f95df52b705f40ad353a7df2e599b59c9f6cc6c7c9e
- TakerPaymentSent · TakerPaymentReceived: 8fc54e3dab42e82636de61c4812aeca1bf5d3f017f4e8a3f8c631a425e89c9e7
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.