XMY/KMD · swap

c0ac1b41-83ae-4d6c-886d-3298ba2ece84

Buy · 2025-11-16 10:04:14 UTC ·

What was traded
Price0.0029654621 KMD
XMY amount25,123
KMD amount74.5
≈ USD$3.60
outside the lookback window
How long it took
Started2025-11-16 09:15:32 UTC
Finished2025-11-16 10:04:14 UTC
Took48m 42s

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:1959] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1763296034 for transaction to be confirmed 3 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 60a1014db345ff13073649806543dbb15a37f1ca547f746ca5a36ca2e90b4484. Checked 2026-09-22 12:51:04 UTC.

On-chain evidence
✓✓✓maker leg · XMY-segwitfrom the swap record

9f465a36db03f9d89158b65811084df96674f463ff88bfe9d0f27ca361252564

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

  • MakerPaymentReceived · MakerPaymentSent: 9f465a36db03f9d89158b65811084df96674f463ff88bfe9d0f27ca361252564
  • MakerPaymentSpent: 60a1014db345ff13073649806543dbb15a37f1ca547f746ca5a36ca2e90b4484
✓✓✓taker leg · KMDfrom the swap record

7fe9378109eb82acdb5d6651cf44ccb1d8f086152d9097d96218dac4057109bb

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

  • TakerFeeSent · TakerFeeValidated: 3581e75a35f285974e6267f0b2f24d97e2e73029f27a34f328d4ed1c7532d594
  • TakerPaymentSent · TakerPaymentReceived: 7fe9378109eb82acdb5d6651cf44ccb1d8f086152d9097d96218dac4057109bb
  • TakerPaymentSpent: b0105550297557ecc12e6b41018ce3d210451353408c7d29e9f7cb94548c9205
Who traded
7cca7b82
Taker524ac60d
Maker clientmympm
Taker client
Versions2.5.2-beta_544c028 · 2.5.1-beta_a9fbf60
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.