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=4415698, 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-06-18 09:37:20 UTC, so the maker can take it back now. Checked 2026-11-06 02:14:30 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.
e58f7c81bb410783551b320e68c928e3c8b5eb01fc433840e31b09d3d79ee251
Both payments are on their chains and locked to the same secret hash 3d810b117ed22291423d2d0df60286e480b41db5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e58f7c81bb410783551b320e68c928e3c8b5eb01fc433840e31b09d3d79ee251
9e8100e4050fb14e5c3e6217a2806e42efdccfd3d00a14e549d51f9892860cd3
Both payments are on their chains and locked to the same secret hash 3d810b117ed22291423d2d0df60286e480b41db5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d4339d5a5db423ce5da29f9ea7b908820963be717f173c3ba9d557a65d77aa55
- TakerPaymentSent · TakerPaymentReceived: 9e8100e4050fb14e5c3e6217a2806e42efdccfd3d00a14e549d51f9892860cd3
- TakerPaymentSpent: 50465a279155c9c41ca4ce7e4a0d0592a928b3622474701c65db419ec7c7b455
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 kdf-statsdb-8762.