BLK/PND · swap

82a67537-16d6-40af-8d9b-bcdedcdd3dc2

Buy · 2025-11-02 11:55:34 UTC ·

What was traded
Price714.3674 PND
BLK amount54.3824
PND amount38,849
≈ USD$3.25
outside the lookback window
How long it took
Started2025-11-02 11:33:34 UTC
Finished2025-11-02 11:55:34 UTC
Took22m 00s

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:2044] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1762094714 for transaction to be confirmed 5 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 ae55a2afe4f1d03e9e944162dcbd11deb5c86a48b6ba367e2472548773bb3100. Checked 2026-09-22 12:52:07 UTC.

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

0755571b897fdb3860a928db79e7eca6a90b2c402356fbfebc7b7cc4ddb159d9

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

  • MakerPaymentSent · MakerPaymentReceived: 0755571b897fdb3860a928db79e7eca6a90b2c402356fbfebc7b7cc4ddb159d9
  • MakerPaymentSpent: ae55a2afe4f1d03e9e944162dcbd11deb5c86a48b6ba367e2472548773bb3100
✓✓✓taker leg · PNDfrom the swap record

4531ebdc5759ed71244ec1ef5bc7a6e358c9ca898f2cc9c6a1676f3c90107d7f

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

  • TakerFeeValidated · TakerFeeSent: 4290e8432ef086c0e093f1d51a2bca26f5614830d2e3a13a28626c4df82507f6
  • TakerPaymentSent · TakerPaymentReceived: 4531ebdc5759ed71244ec1ef5bc7a6e358c9ca898f2cc9c6a1676f3c90107d7f
  • TakerPaymentSpent: 6d41e1365ec722cf92b84a9c75f08f4be1e02ccc942a19a583fdbc33d13f8bc2
Who traded
0e4fab2a
Taker72de8c94
Maker clientPandacoin-multiwallet-DEX 0.8.2-beta
Taker client
Versions2.4.0-beta_f56917b · 2.5.2-beta_bebdc9a17
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.