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:1834] utxo_common:1829] HTLC spend fee 10000000 is greater than transaction output 14695
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 be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch 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 maker can take it back after the timelock. Checked 2026-11-06 05:26:20 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.
ed4e98b60c4c3d49a676c1756294b805b9adacbafac6eae3ba2cb99321eb18c4
Both payments are on their chains and locked to the same secret hash 7bb5d8bb1bc9ec96c0f79efd325d65efc1855821, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ed4e98b60c4c3d49a676c1756294b805b9adacbafac6eae3ba2cb99321eb18c4
e0713d70e320e143b90222da06a8a694a52e36448377c0b1b5bc4e1c737c41cf
Both payments are on their chains and locked to the same secret hash 7bb5d8bb1bc9ec96c0f79efd325d65efc1855821, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5ba69d7af0efbccb8429730b3e6bceb8a8c39735ac5f57290f1edf7637fcb754
- TakerPaymentSent · TakerPaymentReceived: e0713d70e320e143b90222da06a8a694a52e36448377c0b1b5bc4e1c737c41cf
- TakerPaymentSpent: 0749da8a6e5d39718fd00e9dea8f8187aff5a34e71ea1414011140d46ecd0dfc
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.