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 24890020 is greater than transaction output 10442803
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-08 14:43:28 UTC, so the maker can take it back now. Checked 2026-11-06 04:36:47 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.
e95003c56bbb47f274a196822c1e6beca2d4c1e5075a7f98d9660c9ff8c9cfa4
Both payments are on their chains and locked to the same secret hash 4dcad5e801c879ea574f16bd4a719c0cdec23ebc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e95003c56bbb47f274a196822c1e6beca2d4c1e5075a7f98d9660c9ff8c9cfa4
51cc2a225c0a2ea87bfdfa733e27f9c8d7ec69fae2ec30c6ba0f74d48e341efa
Both payments are on their chains and locked to the same secret hash 4dcad5e801c879ea574f16bd4a719c0cdec23ebc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e29f65ae19558493f6da977c3350ff4e24aeeaa543c530e4200fa9c9dab88d24
- TakerPaymentReceived · TakerPaymentSent: 51cc2a225c0a2ea87bfdfa733e27f9c8d7ec69fae2ec30c6ba0f74d48e341efa
- TakerPaymentSpent: 9bba2182dc7953bd5a3a5fd60474fb5b45371bb84938ad428ca0af424bbc60fa
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.