GRS/LTC · swap

b683972a-8f46-4343-9728-b1bb039e948a

Sell · 2026-04-25 10:23:58 UTC ·

What was traded
Price0.00040829185 LTC
GRS amount57.0252
LTC amount0.02328
≈ USD$1.31
outside the lookback window
How long it took
Started2026-04-25 10:23:57 UTC
Finished2026-04-25 16:15:15 UTC
Took5h 51m

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:2052] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1777124136 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 e8e04ab7de39630af8e42d47cd5bf2f7deee423fe50562a551d8f5c2cbaffee4. Checked 2026-09-24 02:06:23 UTC.

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

b6c6a957fe987b8176ad1370a5d7245e34d521c6520d0d0ea57b463a3e78bf10

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

  • MakerPaymentSent · MakerPaymentReceived: b6c6a957fe987b8176ad1370a5d7245e34d521c6520d0d0ea57b463a3e78bf10
  • MakerPaymentSpent: e8e04ab7de39630af8e42d47cd5bf2f7deee423fe50562a551d8f5c2cbaffee4
✓✓✓taker leg · GRSfrom the swap record

a49d96fe306a6b986c813c54333c17f90664e3537c3d5e72d07b5ea4dd1d502a

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

  • TakerFeeSent · TakerFeeValidated: c1cdd1340bf674c9c06d3b6c15617dee361b179e12117fd4df4ca94ada32766e
  • TakerPaymentSent · TakerPaymentReceived: a49d96fe306a6b986c813c54333c17f90664e3537c3d5e72d07b5ea4dd1d502a
  • TakerPaymentSpent: 7929c059d747a421703e12938afba93cd23ba6eed25870fc705df80e71878d81
Who traded
19a2fb83
Takerunknown
Maker clientmympm
Taker client
Versions3.0.0-beta_e686ef3 · 3.0.0-beta_d56a7bc50
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.