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 8415771
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-01 05:23:01 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.
41022f4e3141162d9bbe4d00cee2bebf500c4c869b7cf59936580822ccf68e5e
Both payments are on their chains and locked to the same secret hash 78144d9dc344a35948ca03507d5fa48d7ea2cdad, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 41022f4e3141162d9bbe4d00cee2bebf500c4c869b7cf59936580822ccf68e5e
20488f086d3f52426b8d9a26716835a6c1b36ef2f483a5d06133de05294e8783
Both payments are on their chains and locked to the same secret hash 78144d9dc344a35948ca03507d5fa48d7ea2cdad, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 412a078dd2a69b54c122fa5270d7a9f25d22ff4b3e252c53aeb0b718b4049b60
- TakerPaymentSent · TakerPaymentReceived: 20488f086d3f52426b8d9a26716835a6c1b36ef2f483a5d06133de05294e8783
- TakerPaymentSpent: 5062d86ee1d736ac84c4d3457f3d40198939c1540c26086d4b46a4dad9e0b88e
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.