LTC/BTC · swap

0124f38e-8bd7-4067-bb11-a8efdee410a4

Sell · 2026-06-07 17:25:28 UTC ·

What was traded
Price0.00065943297 BTC
LTC amount10.4452
BTC amount0.006888
≈ USD$426.36
outside the lookback window
How long it took
Started2026-06-07 17:25:28 UTC
Finished2026-06-11 11:42:58 UTC
Took3d 18h

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:2050] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1780888029 for transaction to be confirmed 1 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 d772bee69318988e91c8301d1718d61bfb061d4fa6aac512412359d0868e22a4. Checked 2026-09-22 12:39:37 UTC.

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

789b5b5e419580f4d22caf26b3fd7267791191090b28c7aa1f1d74eba73dc3c9

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

  • MakerPaymentSent · MakerPaymentReceived: 789b5b5e419580f4d22caf26b3fd7267791191090b28c7aa1f1d74eba73dc3c9
  • MakerPaymentSpent: d772bee69318988e91c8301d1718d61bfb061d4fa6aac512412359d0868e22a4
✓✓✓taker leg · LTC-segwitfrom the swap record

10f84f9183ad631c355f18a13065cdcbb26643273ec8680f8d9ef06ff74fe271

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

  • TakerFeeSent · TakerFeeValidated: 0f6fec74ee523f4ccc8194dbf3210f9cda62d0841321cd8268f9281307d156fb
  • TakerPaymentSent · TakerPaymentReceived: 10f84f9183ad631c355f18a13065cdcbb26643273ec8680f8d9ef06ff74fe271
  • TakerPaymentSpent: c7d6f1efe593d0f31e3a10c12cf584785496c01d28475c9812fe685340ee3a0b
Who traded
6374243e
Taker3bfc79b3
Maker clientDEVDOCS_CLI
Taker client
Versions2.6.0-beta_a12695e · 2.6.0-beta_475cdb4
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.