GRS/LTC · swap

9ae15e9d-7606-4c38-b621-255e30432fff

Sell · 2026-09-20 13:54:27 UTC ·

What was traded
Price0.0004381092 LTC
GRS amount133.5549
LTC amount0.05851
≈ USD$3.37
outside the lookback window
How long it took
Started2026-09-20 13:16:04 UTC
Finished2026-09-20 13:54:27 UTC
Took38m 23s

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 1789921663 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 8d7ca75ce5e50c7852a536f90f975dd78fdd5028160db8549d05291e6bf3baeb. Checked 2026-09-22 12:35:22 UTC.

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

9d941265ed4615e05d40ee0af34e3b7c00170c446ed2f9ee7b6c36f4b10ce56a

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

  • MakerPaymentSent · MakerPaymentReceived: 9d941265ed4615e05d40ee0af34e3b7c00170c446ed2f9ee7b6c36f4b10ce56a
  • MakerPaymentSpent: 8d7ca75ce5e50c7852a536f90f975dd78fdd5028160db8549d05291e6bf3baeb
✓✓✓taker leg · GRSfrom the swap record

728856344d7a9dbccc5a455041adc01acc7f6d278cf45174dfe5444c2b32a6f1

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

  • TakerFeeSent · TakerFeeValidated: e32f3e227d344e0c664ac8cf3615aae9dda068e175c3cb02e14b9ee4cb651535
  • TakerPaymentSent · TakerPaymentReceived: 728856344d7a9dbccc5a455041adc01acc7f6d278cf45174dfe5444c2b32a6f1
  • TakerPaymentSpent: a1042f61992459b86a1b574ae4c68af5adf1d21797c1f889958ad6d71dc7d143
Who traded
07699623
Takerad738d3a
Maker clientmympm
Taker client
Versions3.0.0-beta_df8d86b · 3.1.0-beta_f3efd2c
Flags

Reported by kdf-statsdb.