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=4474285, 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 09:30:45 UTC, so the maker can take it back now. Checked 2026-11-06 02:04:29 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.
7d73a081e356413bf7ea4f1b0a249562c4945e9d5d57d220a2b4e8a4984f54a0
Both payments are on their chains and locked to the same secret hash 7f224bdd6f04d69415e2b1799f49643f2fb1e613, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7d73a081e356413bf7ea4f1b0a249562c4945e9d5d57d220a2b4e8a4984f54a0
8c652765880e86aa85506a57a6c4770f6ebf95ed357703d8c3258c401dbcf35c
Both payments are on their chains and locked to the same secret hash 7f224bdd6f04d69415e2b1799f49643f2fb1e613, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 95ffa93cd74ad4e94e5d03782f15bad34da0aa89be5fd84f04f9449b79b62aea
- TakerPaymentSent · TakerPaymentReceived: 8c652765880e86aa85506a57a6c4770f6ebf95ed357703d8c3258c401dbcf35c
- TakerPaymentSpent: 70090c498d06477e9ca313b7a6d0d3bb8ec4562078fcc1c461eb7f40c53af16b
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.