BLK/KMD · swap

59231ca3-b186-45bb-ad1c-191b56cd5400

Sell · 2025-11-07 14:35:35 UTC ·

What was traded
Price0.9639261 KMD
BLK amount83.9657
KMD amount80.9368
≈ USD$3.10
outside the lookback window
How long it took
Started2025-11-07 10:55:16 UTC
Finished2025-11-07 14:35:35 UTC
Took3h 40m

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:2044] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1762547816 for transaction to be confirmed 2 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 bee9fdb9bd89cde49d4a80c6bc5e5c66f3992458caa770a298493152e15db560. Checked 2026-09-22 12:51:38 UTC.

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

bca82f644ae22efa5a610b45916d1ee101340a3f39a8945054418c9aec0b329c

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

  • MakerPaymentSent · MakerPaymentReceived: bca82f644ae22efa5a610b45916d1ee101340a3f39a8945054418c9aec0b329c
  • MakerPaymentSpent: bee9fdb9bd89cde49d4a80c6bc5e5c66f3992458caa770a298493152e15db560
✓✓✓taker leg · BLKfrom the swap record

d816761ddf8db6a070a66a81c7478d31e37a2bfff92c21828d23f3947741e10b

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

  • TakerFeeSent · TakerFeeValidated: 1a119c7f7ac0e4eb789fb719ac84428f2b6c52098c90457864d2f58495ca7338
  • TakerPaymentSent · TakerPaymentReceived: d816761ddf8db6a070a66a81c7478d31e37a2bfff92c21828d23f3947741e10b
  • TakerPaymentSpent: 760854e10fea9a11d7515937c2de71bb2e730e48c24157e8215042a8715be353
Who traded
19a2fb83
Taker524ac60d
Maker clientmympm
Taker client
Versions2.5.2-beta_544c028 · 2.5.2-beta_bebdc9a17
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.