That is in the normal range for CHTA/KMD. 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] mm2src\coins\utxo\ "utxo_common:941] utxo_common:894] client:1057] UnexpectedEnd"
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:17 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.
69a43f7825d20dacc16feecdbfc3f465d3d29a631051c2e8549ef16373b52b0e
Both payments are on their chains and locked to the same secret hash 7b0d30c763e9d19ef62c3953708427b1a6e2942b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 69a43f7825d20dacc16feecdbfc3f465d3d29a631051c2e8549ef16373b52b0e
b4e26fdf0d3c5a369f09c3475978c86402e8bb3ebe2db10b770c8cf8ea26d06f
Both payments are on their chains and locked to the same secret hash 7b0d30c763e9d19ef62c3953708427b1a6e2942b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: fd9f08c3af20c1020f9c74a2c5ae77331841ebaf7e5638f5078c57384428a055
- TakerPaymentSent · TakerPaymentReceived: b4e26fdf0d3c5a369f09c3475978c86402e8bb3ebe2db10b770c8cf8ea26d06f
- TakerPaymentSpent: 031800b84ef131e10512403a038ba173509a843b2f17c3af6cbfea6e3327fcc4
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.