KMD/USDT · swap

1f9e5f58-a9d3-4959-b60f-b27fd27031fb

Sell · 2025-11-14 08:29:03 UTC ·

What was traded
Price0.045882938 USDT
KMD amount5,449
USDT amount250
≈ USD
not evaluated
How long it took
Started2025-11-14 08:29:03 UTC
Finished2025-11-14 08:37:13 UTC
Took8m 10s

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 while the timelock holds.

taker_swap:2004] "eth:2892] request MethodCall(MethodCall { jsonrpc: Some(V2), method: "eth_sendRawTransaction", params: Array([String("0xf9010c8209008405f5e10083014c0894edc5b89fe1f0382f9e4316069971d90a0951db3180b8a402ed292b9249fea3eab5f5e1531bb374a3c8ccbf01a2c7955718a0b90fa44b8c4b1b701b00000000000…

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 timelock holds, and whether it was is a question for the chain rather than for this log.

The chain says the claim landed: the swap contract records the payment as spent by the receiver. Checked 2026-09-22 15:40:33 UTC.

On-chain evidence
✓✓✓maker leg · USDT-BEP20from the swap record

e82e71eec030739f7b1cbefca71317b76295f2a1ae335125ba537265731f2793

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

  • MakerPaymentSent · e82e71eec030739f7b1cbefca71317b76295f2a1ae335125ba537265731f2793
  • MakerPaymentReceived · e82e71eec030739f7b1cbefca71317b76295f2a1ae335125ba537265731f2793
✓✓✓taker leg · KMDfrom the swap record

81050bafe25d22b666da6989034808dc04e7d504f548e2d3ebfe103fb269cc01

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

  • TakerFeeValidated · 14b5df8d34e5233ffaefdac52984f7502742bf82d6d9cc4953d11ff9c14b9dcf
  • TakerPaymentReceived · 81050bafe25d22b666da6989034808dc04e7d504f548e2d3ebfe103fb269cc01
  • TakerPaymentSpent · e83edf2960c80e524792ac470e72b82c93dc0b382b3f044d8fd3f4499f44341a
  • TakerFeeSent · 14b5df8d34e5233ffaefdac52984f7502742bf82d6d9cc4953d11ff9c14b9dcf
  • TakerPaymentSent · 81050bafe25d22b666da6989034808dc04e7d504f548e2d3ebfe103fb269cc01
Who traded
19a2fb83
Takerunknown
Maker clientmympm
Taker client
Versions2.5.2-beta_2b35f2a
Flags

No anomalies were recorded against this swap.

Reported by defistats-gleec.

KMD/USDT swap 1f9e5f58 · SwapScope