That is in the normal range for BTCZ/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 MakerPaymentSpendConfirmFailed. The taker's claim on the maker's coin was broadcast but not seen to confirm.
taker_swap:2052] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1794250418 for transaction to be confirmed 2 times
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 says the claim landed: the payment was spent with the preimage, in 9c9cf37f14364f2a9ccb9b5925eaf7f41449b4723a4cd1f824b946f2947e35c2. Checked 2026-11-09 18:56:29 UTC.
f69e72624f5b51e5b4d6678541d70093d8406923226acf14e51f933cb9004f06
Both payments are on their chains and locked to the same secret hash c090c03c76d858a50c5ccf555a6d7ec74f588710, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: f69e72624f5b51e5b4d6678541d70093d8406923226acf14e51f933cb9004f06
83789c0dace2473a21f7f80ba13088c1b77431be4e5df9325836b1512f648d95
Both payments are on their chains and locked to the same secret hash c090c03c76d858a50c5ccf555a6d7ec74f588710, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 80dbaab89edcaba5b4ab8e977fb35f75e9e809151d905d3074c34c9461b3c0c4
- TakerPaymentReceived: 83789c0dace2473a21f7f80ba13088c1b77431be4e5df9325836b1512f648d95
- TakerPaymentSpent: 70d6bec53da2aba4f5f03f4d99956eb0a764b3f7e705cd0e80b9937f73f7d19f
Reported by kdf-statsdb.