That is in the normal range for LCC/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:1915] utxo_common:1904] HTLC spend fee 10000000 is greater than transaction output 3382592
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 2026-05-03 10:14:57 UTC, so the maker can take it back now. Checked 2026-11-06 02:34:34 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.
8c62609144b9d7f379ec6821982c69718b8206ffebb96c7bdff60d15bb902a67
Both payments are on their chains and locked to the same secret hash 6e687744544f11d4e24b2226f008762029caeeaa, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 8c62609144b9d7f379ec6821982c69718b8206ffebb96c7bdff60d15bb902a67
c3d1ee1ee981bd365c780fee107bc58ba345016b74b71be361dd570f5aac8609
Both payments are on their chains and locked to the same secret hash 6e687744544f11d4e24b2226f008762029caeeaa, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f97cf804bc34b5c63215acd88d6e5cd5d3e043286cb37422c6a85d97d2286aad
- TakerPaymentSent · TakerPaymentReceived: c3d1ee1ee981bd365c780fee107bc58ba345016b74b71be361dd570f5aac8609
- TakerPaymentSpent: 86c218ba484ab5c7d6d5629abde6c735ec991aa381f450286dfd2b83a249773f
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.