That is in the normal range for NENG/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:1803] utxo_common:2035] HTLC spend fee 10000000 is greater than transaction output 5918006
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-09-05 16:38:21 UTC, so the maker can take it back now. Checked 2026-11-06 05:05:32 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.
a32508d86b9036028b406aed9d0e7a121e757b0dacde2698beea8f55f34ac88a
Both payments are on their chains and locked to the same secret hash 01b2fa4abfdba3e09223e89f90889ebd7fc233f6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a32508d86b9036028b406aed9d0e7a121e757b0dacde2698beea8f55f34ac88a
b55bd549c7e9a0ec54f12e0f787c971904d06a8f1a9ef9f48f2e7c6bd4f903c7
Both payments are on their chains and locked to the same secret hash 01b2fa4abfdba3e09223e89f90889ebd7fc233f6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0cc2212b2fc27576b6dd0b197a7ef2be8f9abb387f0f302255120ec840919eb8
- TakerPaymentSent · TakerPaymentReceived: b55bd549c7e9a0ec54f12e0f787c971904d06a8f1a9ef9f48f2e7c6bd4f903c7
- TakerPaymentSpent: 55df524c6fb69a9449effb6796a663d3679faf04ff1f3f9e2cebbfe5b6612fce
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.