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 24938597 is greater than transaction output 10195920
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-21 23:19:11 UTC, so the taker can take it back now. Checked 2026-11-06 05:04:50 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.
bc2044a87ca13f2c2b9465fcbb8461b7b7aec8445cec1cad4df4c03a7995faa6
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: bc2044a87ca13f2c2b9465fcbb8461b7b7aec8445cec1cad4df4c03a7995faa6
- MakerPaymentRefunded: 76f432d31fff9bad7cd7fba1e46530703f126943ed52dfe9763bdc280495fc37
8d0e9a73d647b88fe9085b79d1196d30458ba410ac5ca6333c4956a73193b242
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: f51015fadc444a63a867c64e5257bf2ace28857adb061bb7ab49b1c5530482fd
- TakerPaymentSent · TakerPaymentReceived: 8d0e9a73d647b88fe9085b79d1196d30458ba410ac5ca6333c4956a73193b242
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.