DGC/KMD · swap

b177e528-891d-4668-9dda-5eef01f35641

Sell · 2025-11-16 18:17:30 UTC ·

What was traded
Price0.055001325 KMD
DGC amount90.435
KMD amount4.974
≈ USD$0.2406
outside the lookback window
How long it took
Started2025-11-16 14:06:44 UTC
Finished2025-11-16 18:17:30 UTC
Took4h 10m

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:1953] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1763336904 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 800b0d6eb853ff0abfe1f0eabae792d54ec5cabff7872c95be027ec4b40517e7. Checked 2026-09-22 12:50:59 UTC.

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

20ff228fb84af085597d4cb66e23148c444e01c7a9d5f6cb6977db9292cb0aff

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

  • MakerPaymentSent · MakerPaymentReceived: 20ff228fb84af085597d4cb66e23148c444e01c7a9d5f6cb6977db9292cb0aff
  • MakerPaymentSpent: 800b0d6eb853ff0abfe1f0eabae792d54ec5cabff7872c95be027ec4b40517e7
✓✓✓taker leg · DGCfrom the swap record

ee256aae2f50a33aea72fa7ca195fd3b1b69c8d87f53a6e7434aae8328baadb4

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

  • TakerFeeSent · TakerFeeValidated: 09ab1b216be4fc3fa56b3d6ab4d34ff343dbd2dd101585c4724bd851eb037302
  • TakerPaymentSent · TakerPaymentReceived: ee256aae2f50a33aea72fa7ca195fd3b1b69c8d87f53a6e7434aae8328baadb4
  • TakerPaymentSpent: 835e5d016355c9952248e9e6aae5c75126312134631ad11928798d0bd2343770
Who traded
7cca7b82
Taker524ac60d
Maker clientmympm
Taker client
Versions2.5.2-beta_544c028 · 2.4.0-beta_v2.4.0-beta
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.