That is in the normal range for LCC/DOGE. 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 24907556 is greater than transaction output 11068265
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-03-04 22:32:29 UTC, so the maker can take it back now. Checked 2026-11-06 04:37:55 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.
003befe58b96098d43370b547bb63460e26e50e1018488dbe43820b4eaf60750
Both payments are on their chains and locked to the same secret hash 7c0148da6173684a4aed0746d6a49bb2f19b75fb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 003befe58b96098d43370b547bb63460e26e50e1018488dbe43820b4eaf60750
94f7483b945113a97a55dfc33bb5a03becaa81a854634ecb0761656d652038b4
Both payments are on their chains and locked to the same secret hash 7c0148da6173684a4aed0746d6a49bb2f19b75fb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b924d1df1279fb4bab78beb71df402ef1343785c02e2231549273b16e2c4673b
- TakerPaymentSent · TakerPaymentReceived: 94f7483b945113a97a55dfc33bb5a03becaa81a854634ecb0761656d652038b4
- TakerPaymentSpent: 0b7426f25f9fa1c4fd0c6b8d94430d90f67cb8fa246412b43a879fc04566eb01
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.