VTC/DASH · swap

e85131cc-e2e5-49f8-b690-f31041235cef

Sell · 2026-09-04 17:14:27 UTC ·

What was traded
Price0.0010791001 DASH
VTC amount6.9761
DASH amount0.007528
≈ USD$0.3934
outside the lookback window
How long it took
Started2026-09-04 17:14:27 UTC
Finished2026-09-04 23:56:24 UTC
Took6h 41m

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 1788553567 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 40b3c4d1d4acd13fb0c9d8c9a2ddd9c75487e36bc7b4b62eb18a54fe4bc4d3a2. Checked 2026-09-22 12:35:53 UTC.

On-chain evidence
✓✓✓maker leg · DASHfrom the swap record

36422065344e7e29dcafd5db6bca776a66b69c90ee2a4e741891423b387b3ebd

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

  • MakerPaymentSent · MakerPaymentReceived: 36422065344e7e29dcafd5db6bca776a66b69c90ee2a4e741891423b387b3ebd
  • MakerPaymentSpent: 40b3c4d1d4acd13fb0c9d8c9a2ddd9c75487e36bc7b4b62eb18a54fe4bc4d3a2
✓✓✓taker leg · VTC-segwitfrom the swap record

9a6071f9eefa2a51e47b0a9bbe8081d252507c6e896525b8cb234dc8cb0bac23

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

  • TakerFeeSent · TakerFeeValidated: 80e63b092687ba7baf08ac661b42b3d6a975c4dcafb4a17c67c29d3d9113558f
  • TakerPaymentReceived · TakerPaymentSent: 9a6071f9eefa2a51e47b0a9bbe8081d252507c6e896525b8cb234dc8cb0bac23
  • TakerPaymentSpent: 30708f56de31623a32f1a59654bb0b5360f7e9c7903a62420cd335121359fb03
Who traded
55a49826
Takere7f73815
Maker clientDEV_CLI
Taker client
Versions2.6.0-beta_475cdb49b · 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.