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:2010] "utxo_common:1025] utxo_common:977] client:1132] : failed to parse list of 11 headers (coin=FLUX, from=2591802, requested_count=11): UnexpectedEnd"
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 2026-05-13 02:31:15 UTC, so the maker can take it back now. Checked 2026-11-06 02:34:31 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.
abf622a78d3f2de005339135e6ce4b56b8da346728d12f5572b0957f3d9933fd
Both payments are on their chains and locked to the same secret hash 1344f154afca364fdd6f7594f1c493069b78c020, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: abf622a78d3f2de005339135e6ce4b56b8da346728d12f5572b0957f3d9933fd
6b37b1ed19196d29d1ae4f2189f4a52f7a49427e6266c0029971b513ae5f77ab
Both payments are on their chains and locked to the same secret hash 1344f154afca364fdd6f7594f1c493069b78c020, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2f2ef31d698b7b7a10a82cd25aa7cdde73043787de7244a704908ccc5e190709
- TakerPaymentSent · TakerPaymentReceived: 6b37b1ed19196d29d1ae4f2189f4a52f7a49427e6266c0029971b513ae5f77ab
- TakerPaymentSpent: 92b8b80d497f68c382eeee544da3fa27a5949143e05c7106690a5cef3e4c6e64
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.