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.
5fc42d869b7b7de7a53b0db6f0aefbdbaa010061d97914907613ba3ccd74e39d
Both payments are on their chains and locked to the same secret hash e9739854e5e9cc362ee29f015b6db0d36437a0e8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5fc42d869b7b7de7a53b0db6f0aefbdbaa010061d97914907613ba3ccd74e39d
09631cbba60a2e1afb3e2af726a3793cba069d9fedc677531a798dfc6ef15d3c
Both payments are on their chains and locked to the same secret hash e9739854e5e9cc362ee29f015b6db0d36437a0e8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 5f4f6b08ae5bb637676710a7a0f8356889403ebc0769925366936cb253b05026
- TakerPaymentSent · TakerPaymentReceived: 09631cbba60a2e1afb3e2af726a3793cba069d9fedc677531a798dfc6ef15d3c
- TakerPaymentSpent: ecf27c046eff2907fa0f7c9ac8a132df2be6d9d44880bd51c2394422a1a79025
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.