That is in the normal range for LBC/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 1794347948 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 dbbb8d6b661dddb2fc327a3677875ce8ab6070ec2d080e566c625b7509f53273. Checked 2026-11-10 22:47:35 UTC.
a10bf11abbdbbd01e269f4e7c76c439a2d18ea5356ee2c62865928ad8b5bf326
Both payments are on their chains and locked to the same secret hash ed5b786dd5a81c2adfa8e46c5497e55609b69fee, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: a10bf11abbdbbd01e269f4e7c76c439a2d18ea5356ee2c62865928ad8b5bf326
68921f15c655fe6e983d3a4b68c5e8af16c4012b4fe0647fd7ece546106ad505
Both payments are on their chains and locked to the same secret hash ed5b786dd5a81c2adfa8e46c5497e55609b69fee, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 6ff9820562f5dd497cb2e1c85bd510508d8f4d0e7010371aa86c7f26697928a5
- TakerPaymentReceived: 68921f15c655fe6e983d3a4b68c5e8af16c4012b4fe0647fd7ece546106ad505
- TakerPaymentSpent: af77d2e487875cdb30c8803beab226d4cdd8fd509ad7a7614073f46eae58e0cf
Reported by kdf-statsdb.