This one took about 4.2× the usual for CHTA/KMD. Waiting longer than usual is not in itself a failure: a swap waits on confirmations from both chains, and a slow block or a busy network stretches it.
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 still be made for as long as the payment is unspent, and since the timelock has passed the payer can take it back as well, so whichever lands first settles 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 timelock expired 2025-12-08 01:37:46 UTC, so the maker can take it back now. Checked 2026-11-06 04:52:34 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.
17d81ce7cef5b708c3e3dba0920ddbe6df8a75a11d4e356d7d8ad9a8ce3850b6
Both payments are on their chains and locked to the same secret hash 2cef5088942f1dc0868ff6039624563d840e7777, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 17d81ce7cef5b708c3e3dba0920ddbe6df8a75a11d4e356d7d8ad9a8ce3850b6
12d264bae1bb890c35444f7d7b9d5870fae28e2f5b7701a650d9f4770aea8372
Both payments are on their chains and locked to the same secret hash 2cef5088942f1dc0868ff6039624563d840e7777, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 845bcd377ed5dd817cb49da5a62c45a442cd8e7da2a6c443db069702007f2c72
- TakerPaymentSent · TakerPaymentReceived: 12d264bae1bb890c35444f7d7b9d5870fae28e2f5b7701a650d9f4770aea8372
- TakerPaymentSpent: c032b0202a9c9c8e5ca13b196d03809273212635571b7c6c8e9a4932f916a6f5
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.