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 24950938 is greater than transaction output 10001630
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-17 02:53:38 UTC, so the taker can take it back now. Checked 2026-11-06 05:04:53 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.
0717fe906d1db6b783f4039bbb1e9b4a34c043c52d060d5a397fcf3b03df7319
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentReceived · MakerPaymentSent: 0717fe906d1db6b783f4039bbb1e9b4a34c043c52d060d5a397fcf3b03df7319
- MakerPaymentRefunded: 29d10b431e039035cf36762e3c486ef5aa27a8df8494a9c90c2152cd2f54f458
0e6dc5c33beef2ebda0fde33fd819e8bc690d492252bddfae7738ca9eb13ead0
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 63859e3d819911b2019bd8d8e7a72743773da9db2b77e624bd843ce6f714c4a1
- TakerPaymentSent · TakerPaymentReceived: 0e6dc5c33beef2ebda0fde33fd819e8bc690d492252bddfae7738ca9eb13ead0
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.