That is in the normal range for CHTA/DGB. 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:1834] utxo_common:1829] HTLC spend fee 10000000 is greater than transaction output 1115843
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 be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch 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 maker can take it back after the timelock. Checked 2026-11-06 05:15:16 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.
8db1a452a07fb27029f793837ae128b9fd8cfd446c9e2c70443852234fac103d
Both payments are on their chains and locked to the same secret hash 6f962eeec27e01d64336df5f20dbdc639ce4cf01, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8db1a452a07fb27029f793837ae128b9fd8cfd446c9e2c70443852234fac103d
41fa8be39e5b31101b99cc5e2266c6698ac19a17a47d7db79a61a8d88b7de046
Both payments are on their chains and locked to the same secret hash 6f962eeec27e01d64336df5f20dbdc639ce4cf01, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 7a5739c532aeceb608de6b3473f7ad916b5d985fcf35ed88c60b3cd87378f2e5
- TakerPaymentReceived · TakerPaymentSent: 41fa8be39e5b31101b99cc5e2266c6698ac19a17a47d7db79a61a8d88b7de046
- TakerPaymentSpent: a0340add22b0f70451b43ea55156373b0db01c8d21ccd302acfdb3fd0cb06604
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.