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:1803] utxo_common:2035] HTLC spend fee 10000000 is greater than transaction output 1973568
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:05:16 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.
907b6bb689ddc4aa6db6eb13ec35be319102be94d7cb342cbe73c6f961eac29a
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 907b6bb689ddc4aa6db6eb13ec35be319102be94d7cb342cbe73c6f961eac29a
0b702d002b9d608471384aa2fd910a2a046080dd9fab5b921691585fc288a977
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeValidated · TakerFeeSent: bb926b9a4388a42c63b5d29ada46aa8b1b4dae562c40301bf7c162abf291fe93
- TakerPaymentReceived · TakerPaymentSent: 0b702d002b9d608471384aa2fd910a2a046080dd9fab5b921691585fc288a977
- TakerPaymentSpent: f2f3dce8fcb6352a070f679a9968a12adee83e0675a961ecc6fba16a7674c5f2
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.