BTC/LTC · swap

9dc4fa95-9caa-410e-a9f0-653025fc4d79

Buy · 2026-07-21 00:31:15 UTC ·

What was traded
Price1,391.39 LTC
BTC amount0.00095
LTC amount1.3218
≈ USD$62.62
outside the lookback window
How long it took
Started2026-07-21 00:31:15 UTC
Finished2026-07-21 00:42:14 UTC
Took10m 59s

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 for as long as that payment is unspent.

taker_swap:2010] "eth:3092] request MethodCall(MethodCall { jsonrpc: Some(V2), method: "eth_sendRawTransaction", params: Array([String("0xf901088201368083014c0894edc5b89fe1f0382f9e4316069971d90a0951db3180b8a402ed292b652eb51c109ee05e1275b9c17083e7dc59b34c9d3b6178c15ba793c8b2c1d1370000000000000000000…

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 swap contract records the payment as spent by the receiver. Checked 2026-09-22 15:40:30 UTC.

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

142dd37a2ab6199620973a5c4a408f54e690ab422c01f09d6223d29e2318f305

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

  • MakerPaymentSent · MakerPaymentReceived: 142dd37a2ab6199620973a5c4a408f54e690ab422c01f09d6223d29e2318f305
✓✓✓taker leg · LTC-segwitfrom the swap record

43c5947b4d3f421319e3c54b3f7cba7c3cafe5347fb04ce6cbdc7e9ffd668b14

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

  • TakerFeeSent · TakerFeeValidated: 436655770ef005c7055e7b1ba7391662df0d39aa8376b921cd73792e1380c614
  • TakerPaymentSent · TakerPaymentReceived: 43c5947b4d3f421319e3c54b3f7cba7c3cafe5347fb04ce6cbdc7e9ffd668b14
  • TakerPaymentSpent: 67340bee1c80543bb28d442663771793fd2b67587ff14c9d27de6f777b81ea10
Who traded
11d3c81e
Taker09d71a49
Maker clientDEVDOCS_CLI
Taker client
Versions2.6.0-beta_a12695e · 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.