KMDCL/KMD · swap

4191d75b-38fc-468a-8ee7-8a066839d947

Sell · 2026-09-08 22:08:57 UTC ·

What was traded
Price5.2232 KMD
KMDCL amount1.9145
KMD amount10
≈ USD$0.0637
outside the lookback window
How long it took
Started2026-09-08 22:08:57 UTC
Finished2026-09-09 03:23:21 UTC
Took5h 14m

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 MakerPaymentSpendConfirmFailed. The taker's claim on the maker's coin was broadcast but not seen to confirm.

taker_swap:2052] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1788916837 for transaction to be confirmed 1 times

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 says the claim landed: the payment was spent with the preimage, in 1f1b1d32c483d0b0836ae8ec2d62b3a11bf2a0facc78c086257c32b51fc70d51. Checked 2026-09-22 12:35:39 UTC.

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

d59039578d6463ab2353dc91f9d0f885857fc942cf716cf051f6f8c6f82a3a5e

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

  • MakerPaymentSent · MakerPaymentReceived: d59039578d6463ab2353dc91f9d0f885857fc942cf716cf051f6f8c6f82a3a5e
  • MakerPaymentSpent: 1f1b1d32c483d0b0836ae8ec2d62b3a11bf2a0facc78c086257c32b51fc70d51
✓✓✓taker leg · KMDCLfrom the swap record

154c0268bf954398205e9c17c5c2adbc958719facb1c87ee3ee545628a8328d0

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

  • TakerFeeSent · TakerFeeValidated: 14f6b83af4cc30fc7065e19bd3647cf85641a94be6fafdde81ab639074adcf2f
  • TakerPaymentSent · TakerPaymentReceived: 154c0268bf954398205e9c17c5c2adbc958719facb1c87ee3ee545628a8328d0
  • TakerPaymentSpent: 2b94f9c1b3e4b3d818c6c9cc0fe12165a6e1a510f3c4a3a2d5de4e9f17c9d4c3
Who traded
67f5ad80
Takere7f73815
Maker clientLitecoin Cash DEX 1.0.0
Taker client
Versions2.6.0-beta_475cdb4 · 2.6.0-beta_a12695e
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.