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 182183
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:15:15 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.
e712a50204ad0e273e28570c1e628fead0afe54322e7a7d2c18b82b368fda37d
Both payments are on their chains and locked to the same secret hash ff4fd71c03a79b39adea6bda3b0c3592a5dcb5c6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: e712a50204ad0e273e28570c1e628fead0afe54322e7a7d2c18b82b368fda37d
0e3ea9e17f1d00c62b7029a060f94ff89da20f40503e079df3b0d44297354dd4
Both payments are on their chains and locked to the same secret hash ff4fd71c03a79b39adea6bda3b0c3592a5dcb5c6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bff44bfc055f9365479746924e7b7b8f96bebdb23bc64093a30b1439a6faaf2b
- TakerPaymentSent · TakerPaymentReceived: 0e3ea9e17f1d00c62b7029a060f94ff89da20f40503e079df3b0d44297354dd4
- TakerPaymentSpent: 870ad4bfc24895b64fa39d907b51a34664b32a467d7e500317bd80362b6926ba
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.