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.
7822551af0df5c76ea5bc9f96d2a4a7f077f526883de7ee565f3fb4a2fc47f8a
Both payments are on their chains and locked to the same secret hash d6020ec38bd44e24a7ffdce7e333dc7e54b2203d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 7822551af0df5c76ea5bc9f96d2a4a7f077f526883de7ee565f3fb4a2fc47f8a
30313a277cefcd2e040b94921e6670819b42d7da89a1775b51fff83a40bbfb5a
Both payments are on their chains and locked to the same secret hash d6020ec38bd44e24a7ffdce7e333dc7e54b2203d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0ba463c7564bdd62d3cbd330bf1cbe7226744c136545fbfb1b4167739a771128
- TakerPaymentSent · TakerPaymentReceived: 30313a277cefcd2e040b94921e6670819b42d7da89a1775b51fff83a40bbfb5a
- TakerPaymentSpent: c69e339649ea30daa180b4105f9c2148f68d24ce54912dcbb70036e1334d59dc
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.