That is in the normal range for RVN/LTC. The time a swap takes is set mostly by the block spacing of the two chains involved, so a pair with slow blocks is slow for everyone, every time.
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=4480780, 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-08-02 22:23:00 UTC, so the maker can take it back now. Checked 2026-11-06 01:54: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.
db7232b3579c8986b55835d546300fbbca10c9faa12d326d57defa03549e2f02
Both payments are on their chains and locked to the same secret hash b8154ffc818c75efff6cac7a27ddb1264b9176e2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: db7232b3579c8986b55835d546300fbbca10c9faa12d326d57defa03549e2f02
bd90fe2f9fd88d2f4a937d5b6542509f618f704dc5c05a69fe3320deedc7a9ba
Both payments are on their chains and locked to the same secret hash b8154ffc818c75efff6cac7a27ddb1264b9176e2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ddddcf3a77ff606e40c351197c68eb3a6c8c8457229dd6f4ed1586596437b12e
- TakerPaymentSent · TakerPaymentReceived: bd90fe2f9fd88d2f4a937d5b6542509f618f704dc5c05a69fe3320deedc7a9ba
- TakerPaymentSpent: 47c6ea48e8ef1c2ca7153083eb13298489974ec1df35c1e84e4306da70f81c0f
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.