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:1806] utxo_common:2146] HTLC spend fee 10000000 is greater than transaction output 266971
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-06 06:04:45 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.
817dff78f5da829af242c34755d1a567c1f3cd9ca68ce6abbb1b8b480d6cdbb2
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 817dff78f5da829af242c34755d1a567c1f3cd9ca68ce6abbb1b8b480d6cdbb2
0fd600d6301712f0b3cf5952a0535691b8bcbb16fc71d5faefaef7e3423c1258
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeValidated · TakerFeeSent: 2a652dbc75f3d1942e38097bdf0e546206bfa4d5f7af098708602ace8424d6b5
- TakerPaymentReceived · TakerPaymentSent: 0fd600d6301712f0b3cf5952a0535691b8bcbb16fc71d5faefaef7e3423c1258
- TakerPaymentSpent: e23d913026f4069868de92ed0b05d6231e39ba44deff065048dab0f10b54d1a5
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.