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:1834] utxo_common:1829] HTLC spend fee 15333628 is greater than transaction output 15217181
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 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 timelock expired 2025-10-18 18:17:33 UTC, so the maker can take it back now. Checked 2026-11-06 05:04:51 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.
f8aad3dd93808b81f337505b5e007dc4d5fe185cbd217f4f4c753b62d0e44c29
Both payments are on their chains and locked to the same secret hash 2867ea1c3f468b222bf953c4778e3615b28e6b56, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f8aad3dd93808b81f337505b5e007dc4d5fe185cbd217f4f4c753b62d0e44c29
f1b674e51fc2111840628bf73d82b0ba208d268dda1a4e604e0472d9d07cb43d
Both payments are on their chains and locked to the same secret hash 2867ea1c3f468b222bf953c4778e3615b28e6b56, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7e892d85a321c35d5b827c13470752af88fd0e5e517a044f51e5fa66acad4537
- TakerPaymentSent · TakerPaymentReceived: f1b674e51fc2111840628bf73d82b0ba208d268dda1a4e604e0472d9d07cb43d
- TakerPaymentSpent: 202ef3ba01d5d93994eeb223e22ce1d8fcc7fd22d74d6774c01e78fe394bd0ab
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.