PIVX/USDC · swap

274a28a9-acd7-4d04-9891-2f9d89224ba7

Sell · 2026-01-20 03:41:02 UTC ·

What was traded
Price0.17030629 USDC
PIVX amount80.7661
USDC amount13.755
≈ USD$13.75
outside the lookback window
How long it took
Started2026-01-20 03:41:02 UTC
Finished2026-01-20 20:00:10 UTC
Took16h 19m

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:2050] !wait for maker payment spend confirmations: eth:5744] Timeout: eth:5744] Waited too long until 1768891963 for payment tx:, for coin:USDC-BEP20, to be confirmed!

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 swap contract records the payment as spent by the receiver. Checked 2026-09-22 15:40:32 UTC.

On-chain evidence
✓✓✓maker leg · USDC-BEP20from the swap record

9cb2ffa9c2e67b744e7dc67bc4a2849c9d3a46f5ae90dacf8c8ebcad2aa7cf28

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

  • MakerPaymentSent · MakerPaymentReceived: 9cb2ffa9c2e67b744e7dc67bc4a2849c9d3a46f5ae90dacf8c8ebcad2aa7cf28
  • MakerPaymentSpent: 28e422281b67749776288ef2727f34a4d6d5526545c1069263e968d753b9d2a7
✓✓✓taker leg · PIVXfrom the swap record

e687dce99cc211aacadafc8b3e09a77042869720eb157946ac13ea385e7009f5

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

  • TakerFeeSent · TakerFeeValidated: 33d9b7733e4cbbac71e802d1862f38b103dd5d6479e17318d6313e8337b8d614
  • TakerPaymentSent · TakerPaymentReceived: e687dce99cc211aacadafc8b3e09a77042869720eb157946ac13ea385e7009f5
  • TakerPaymentSpent: bb2f4734d93c713caa66f93d4394fe2258406da316fff4a360970f58fc07743c
Who traded
aed4b579
Taker6e8f3342
Maker clientmympm
Taker client
Versions2.6.0-beta_8404fa5 · 2.6.0-beta_5308356b5
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.