That is in the normal range for DGB/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:2050] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1792908450 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 21ee4af300bfeeff2db8d66cc13b616ea536c5f2ac8255a30fc1d757ca0f079e. Checked 2026-10-26 01:00:14 UTC.
eaee1b41fef3f22fd1bc18677c6242399e1ba29094fd7f721620a9fd39106a20
Both payments are on their chains and locked to the same secret hash 51703af1e45281382beb90e60c217041722d9b61, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: eaee1b41fef3f22fd1bc18677c6242399e1ba29094fd7f721620a9fd39106a20
a1079ec84bf0a4ab8af8a97c5c3da631bf3a315ff52e86ffee87bff4a66c1e7b
Both payments are on their chains and locked to the same secret hash 51703af1e45281382beb90e60c217041722d9b61, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 45b7bbd75983b58671287be789bc0e773d7325d26af49579f322b44742c75efc
- TakerPaymentReceived: a1079ec84bf0a4ab8af8a97c5c3da631bf3a315ff52e86ffee87bff4a66c1e7b
- TakerPaymentSpent: 2e93584a2f6eb7bfa6132f45456e5fa1d677633ab1a61848d0f1a49ffdba7f3d
Reported by kdf-statsdb-8762.