XEC/KMD · swap

1c91868c-74f8-47ad-a7ad-a28aea873f3b

Buy · 2025-08-12 13:35:19 UTC ·

What was traded
Price0.00060996 KMD
XEC amount218.532
KMD amount0.1333
≈ USD$0.004427
outside the lookback window
How long it took
Started2025-08-12 13:35:19 UTC
Finished2025-08-12 14:03:16 UTC
Took27m 57s

An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.

The final claim did not go through on the first attempt

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] mm2src\coins\utxo\ "utxo_common:946] utxo_common:898] client:1066] 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-16 07:13: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.

On-chain evidence
✓✓✓maker leg · XECfrom the swap record

9a187d0f137a9b6bf6d47bcebdcc31c6d40e3b15a52e2913984c6c6b79b41189

Both payments are on their chains and locked to the same secret hash 0b052d16b269c33d7a3976c88c45390864da1341, and a preimage hashing to it was published on chain when one side claimed.

  • MakerPaymentSent · MakerPaymentReceived: 9a187d0f137a9b6bf6d47bcebdcc31c6d40e3b15a52e2913984c6c6b79b41189
✓✓✓taker leg · KMDfrom the swap record

6a41f802170b9dd736e4e6b0a1446e2923608f81736b407784838cfb5538b023

Both payments are on their chains and locked to the same secret hash 0b052d16b269c33d7a3976c88c45390864da1341, and a preimage hashing to it was published on chain when one side claimed.

  • TakerFeeSent · TakerFeeValidated: a16aeed0bce679bbe82d0a78285dc0a9ba5d0014e12e132277872c15405e861d
  • TakerPaymentSent · TakerPaymentReceived: 6a41f802170b9dd736e4e6b0a1446e2923608f81736b407784838cfb5538b023
  • TakerPaymentSpent: 53d15a8ee80e779fd0a565cd9c82b6c2520b7b3ac63f906057bbdb017d0a42ab
Who traded
6374243e
Taker3c9491ee
Maker clientmympm
Taker client
Versions2.5.1-beta_b65af6f · 2.4.0-beta_c800ea03f
Flags

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.