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 MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried for as long as that payment is unspent.
the transaction was rejected by network rules. mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation) (code 16)
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 06:04:53 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.
dad91c16c001d28dcfe639a80e9e42672f060a2790e9e52888bbdeb72e8b759b
Both payments are on their chains and locked to the same secret hash b6ab15ea7ec984751ea9698c35ded7df29b232c4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dad91c16c001d28dcfe639a80e9e42672f060a2790e9e52888bbdeb72e8b759b
1c6865e4eb8d3d2174d86e820dd28cf7044b4d7c97e457fb3a9b08fa028244d2
Both payments are on their chains and locked to the same secret hash b6ab15ea7ec984751ea9698c35ded7df29b232c4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6095de44dd3c8b19565a08a84bebd3557748605fa2182cd074592bd1c142a162
- TakerPaymentReceived · TakerPaymentSent: 1c6865e4eb8d3d2174d86e820dd28cf7044b4d7c97e457fb3a9b08fa028244d2
- TakerPaymentSpent: 7b47ceeb5fd66421cef8a4ac757ee2b5f1f963c87b65798aee75e306c4c06b05
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 kdf-statsdb-8762.