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 8428682
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 02:52:58 UTC, so the maker can take it back now. Checked 2026-11-06 04:56:26 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.
a8d77a9b476ab6f0166efdcddfe09902e9c518b987a6a368343f812b69d1b5c6
Both payments are on their chains and locked to the same secret hash 12574563b009f687b22997d2ac2f1d4e1d6beb1d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: a8d77a9b476ab6f0166efdcddfe09902e9c518b987a6a368343f812b69d1b5c6
6c4e87ff1c8fc2118ea9607e4950c0274b7f3144325d43022dd0f0caec264344
Both payments are on their chains and locked to the same secret hash 12574563b009f687b22997d2ac2f1d4e1d6beb1d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9dc7200b892d5115fe4ef1f1d379b2f86502fe73d18361fe3df6c45d7c09ad0a
- TakerPaymentSent · TakerPaymentReceived: 6c4e87ff1c8fc2118ea9607e4950c0274b7f3144325d43022dd0f0caec264344
- TakerPaymentSpent: 5a60c992114f31b468e552e352a8c47fb91fc130d01a445080b4e616b3503d81
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.