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:1916] utxo_common:1904] HTLC spend fee 100000 is greater than transaction output 54600
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 05:25:08 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.
afc233c5a8cf4638b20817ed686f534c80d94edb7d361479f24c33b2dfcf5afe
Both payments are on their chains and locked to the same secret hash 9424afa69e5fe10afc21120beb658c49cc0da382, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: afc233c5a8cf4638b20817ed686f534c80d94edb7d361479f24c33b2dfcf5afe
d080737d6dec8f575f968f62819f64b863be6d6ef50f8f6d23853eebdb30e231
Both payments are on their chains and locked to the same secret hash 9424afa69e5fe10afc21120beb658c49cc0da382, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5b1405b901fbd2e22e380465960b9d0cb4c76f0072e488f7f788b6d396eebb8e
- TakerPaymentSent · TakerPaymentReceived: d080737d6dec8f575f968f62819f64b863be6d6ef50f8f6d23853eebdb30e231
- TakerPaymentSpent: 0945ef35487d27983c0e355363eb7bbfb3760ce67dd28c7e8732fac061ee138b
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 defistats-gleec.