That is in the normal range for BTCZ/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:1806] utxo_common:2146] HTLC spend fee 10000000 is greater than transaction output 4062500
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 2025-12-19 23:18:27 UTC, so the maker can take it back now. Checked 2026-11-06 04:46:51 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.
50e25e9b4083e5a07f5609ff75e57acb93f05c66ac09b0b8128ca580b9309c0b
Both payments are on their chains and locked to the same secret hash 0a31d7de10402e32a03b030b09aa8544837e9820, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 50e25e9b4083e5a07f5609ff75e57acb93f05c66ac09b0b8128ca580b9309c0b
322ba8f3724d083dcd31abe1fd2cbb343aa675283d98ac3946e7e5b2afa2f29a
Both payments are on their chains and locked to the same secret hash 0a31d7de10402e32a03b030b09aa8544837e9820, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 7e647705aaeb8bcea9a2bc20f64f06b71b40ffbe1ee15136ce85c6a051d9a2bb
- TakerPaymentSent · TakerPaymentReceived: 322ba8f3724d083dcd31abe1fd2cbb343aa675283d98ac3946e7e5b2afa2f29a
- TakerPaymentSpent: 70b5f08d51ea405b1a5b290cf791fe4d84ade9d9e13b5124c4ed98883c1dbb3e
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.