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:1915] utxo_common:1904] HTLC spend fee 10000000 is greater than transaction output 7213674
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-11-09 18:05:25 UTC, so the maker can take it back now. Checked 2026-11-06 04:56:22 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.
eeb0f0530ff757cd1b48dfd85a667d1161ca581045f901f5e94005994f5660ed
Both payments are on their chains and locked to the same secret hash d6000ec42312c62a893089ffd574e5f34b232b46, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: eeb0f0530ff757cd1b48dfd85a667d1161ca581045f901f5e94005994f5660ed
e0881df7e59d4c14554b7951db3b554319dba4f02bbf25e3beda0a01f2b74905
Both payments are on their chains and locked to the same secret hash d6000ec42312c62a893089ffd574e5f34b232b46, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d782cad8f22e55d0127265801afeced5a0f988d4880dcc5dbd9218ae735d56c8
- TakerPaymentSent · TakerPaymentReceived: e0881df7e59d4c14554b7951db3b554319dba4f02bbf25e3beda0a01f2b74905
- TakerPaymentSpent: fd216393ba6b79d48abe2377b5005c20e5b84f24eec524d9f2579e5ab37d6747
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.