PIVX/DASH · swap

db12c350-4da5-44fc-bd66-ae9ba9099cf2

Sell · 2025-07-04 02:56:01 UTC ·

What was traded
Price0.0063752041 DASH
PIVX amount36.8678
DASH amount0.235
≈ USD$4.72
outside the lookback window
How long it took
Started2025-07-04 02:56:00 UTC
Finished2025-07-11 01:42:12 UTC
Took6d 22h

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:1872] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1751609259 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 be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch 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 5ce704fca1639ff8bf23d118612bfe99a6aaec81decbd397fda1394290c16a6b. Checked 2026-09-22 12:57:15 UTC.

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

fb449671a1c32907499fdacaafa8e41734d3875c7e8eaa31fffdb4e0a8dbb6c5

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

  • MakerPaymentReceived · MakerPaymentSent: fb449671a1c32907499fdacaafa8e41734d3875c7e8eaa31fffdb4e0a8dbb6c5
  • MakerPaymentSpent: 5ce704fca1639ff8bf23d118612bfe99a6aaec81decbd397fda1394290c16a6b
✓✓✓taker leg · PIVXfrom the swap record

cd845a2397a133bf74325a899b27c1811681fa0e158fb1351fc75451330ef808

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

  • TakerFeeSent · TakerFeeValidated: 75c196c7f86d72cd4689737e88c8e7dfaa3b32af8c6d5dba57b2cc58383829a6
  • TakerPaymentSent · TakerPaymentReceived: cd845a2397a133bf74325a899b27c1811681fa0e158fb1351fc75451330ef808
  • TakerPaymentSpent: 6a9cf89a06b3ab4b23f481ec4c0f632a7be38cb44e473eb7d32542ebac7bef5e
Who traded
19a2fb83
Taker96c91813
Maker clientmympm
Taker client
Versions2.5.0-beta_438df3c · 2.3.0-beta_2.1.25_gs/v2.3.0-beta_8206c6ef6_Windows_NT_Release
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.