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 TakerPaymentSpendFailed. The maker's claim on the taker's coin was rejected; it can be retried for as long as that payment is unspent.
maker_swap:1269] !taker_coin.send_maker_spends_taker_payment: "utxo_common:1025] utxo_common:977] client:1132] : failed to parse list of 11 headers (coin=RVN, from=4491962, 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 taker's payment still sitting in its contract: neither claimed nor refunded. The maker never collected, so the secret was not revealed and the timelock expired 2026-08-11 00:49:43 UTC, so the taker can take it back now. Checked 2026-11-06 01:44:26 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.
304a3a4a7b0b4f62de6e6358ba8661cf1ad92d27285993432c1b9ede5cf59e40
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 304a3a4a7b0b4f62de6e6358ba8661cf1ad92d27285993432c1b9ede5cf59e40
- MakerPaymentRefunded: 87fd9821e696c5de3a003b1f525f18140f9d5178a93ab6580bdbcd564d987cd1
6d5847c007d3e0aba2aaab26c52728ba8e4f91b232d27cd851f77036f7773824
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 612eab8136cde49d366263a0b7bd57ea4f9c832afd437dfe0885b9c525b50980
- TakerPaymentSent · TakerPaymentReceived: 6d5847c007d3e0aba2aaab26c52728ba8e4f91b232d27cd851f77036f7773824
- TakerPaymentRefunded: 6858022f2a6e6de1a758b4ab676b3002e8045caf2a9a25af5a0ebff86825dbb7
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.