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=4475103, 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 23:06:53 UTC, so the maker can take it back now. Checked 2026-11-16 02:23:19 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.
aca9670f090a9b38b20b7aa9eb3ad47276a067b257b68d8e62136311eb94a3f2
Both payments are on their chains and locked to the same secret hash 105b5e1eb4f8e839be5701ca5a0e455e5e1ee401, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: aca9670f090a9b38b20b7aa9eb3ad47276a067b257b68d8e62136311eb94a3f2
2f53a0c2b13d9843e4bf8250c8e48d715b4efdff7c9adde123c181570cca34d8
Both payments are on their chains and locked to the same secret hash 105b5e1eb4f8e839be5701ca5a0e455e5e1ee401, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b8f493bf3725fad4b33ea44fc1bec7bb908166829f76b7dbf65e03b793d7ec04
- TakerPaymentSent · TakerPaymentReceived: 2f53a0c2b13d9843e4bf8250c8e48d715b4efdff7c9adde123c181570cca34d8
- TakerPaymentSpent: 7c68a047c17a5f8faa8503d75b0c511d2e17a9e9c04a91927332a141d53f96e3
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.