ZEC/BTC · swap

9f8eb9fe-b441-4cc7-b61a-322764ce546d

Sell · 2025-10-26 16:54:20 UTC ·

What was traded
Price0.0029196449 BTC
ZEC amount1.46
BTC amount0.004263
≈ USD$480.61
outside the lookback window
How long it took
Started2025-10-26 16:35:34 UTC
Finished2025-10-26 16:54:20 UTC
Took18m 46s

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:1904] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1761531439 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 9da22fdc3390ab06159c4f0ad3da01e946335708eb2284bdbb6cbc5cbe515e53. Checked 2026-09-22 12:52:23 UTC.

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

e34be1345f17dae51269e206b9b6d0cf1d2acdab8dfc492d493d72ec7d924fb1

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

  • MakerPaymentSent · MakerPaymentReceived: e34be1345f17dae51269e206b9b6d0cf1d2acdab8dfc492d493d72ec7d924fb1
  • MakerPaymentSpent: 9da22fdc3390ab06159c4f0ad3da01e946335708eb2284bdbb6cbc5cbe515e53
✓✓✓taker leg · ZECfrom the swap record

2dab597e3f1dd7e5c9856039c2e6237f79c746cec08c788c42720a437ae3f920

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

  • TakerFeeValidated · TakerFeeSent: d390f200047806cd8a1fdc82b0f93251cb96f458c78789c00c78f66efda36cc6
  • TakerPaymentReceived · TakerPaymentSent: 2dab597e3f1dd7e5c9856039c2e6237f79c746cec08c788c42720a437ae3f920
  • TakerPaymentSpent: 5690a0171ae51c64e153cec6bb4f0da3c7f69ec75efff7697c1e8b5c83fd2f5c
Who traded
a5e467d7
Taker597cf591
Maker clientmympm
Taker client
Versions2.5.2-beta_656487b · 2.3.0-beta_405bcb7
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.