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:2008] mm2src\coins\utxo\ "utxo_common:998] utxo_common:950] client:1132] : failed to parse list of 11 headers (coin=RVN, from=4473829, 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-07-29 02:01:22 UTC, so the maker can take it back now. Checked 2026-11-16 02:33:17 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.
f5f14ab7c2ebaeeca56f3f9de0c8d4286c389c3ffde7dc9df00caa7e8484e608
Both payments are on their chains and locked to the same secret hash 0c68f439bd59f60b7823a35b0dc13b0b5758147a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f5f14ab7c2ebaeeca56f3f9de0c8d4286c389c3ffde7dc9df00caa7e8484e608
0b9a5784c756faba9146a648cf8bd7630234eaa090aaf89cd1482c7955c719ab
Both payments are on their chains and locked to the same secret hash 0c68f439bd59f60b7823a35b0dc13b0b5758147a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 72bbdfb91441c7bbbb7d8085c2a9e73d75794f8f167b53d13e50a42e43d833d8
- TakerPaymentSent · TakerPaymentReceived: 0b9a5784c756faba9146a648cf8bd7630234eaa090aaf89cd1482c7955c719ab
- TakerPaymentSpent: e6dbb3b19b79d0026d8a6ba33058d0ac565081a0493c1cffd3dda678e3ad611c
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.