WHIVE/DGB · swap

462bf857-230d-4076-a1c4-e231df6ab399

Sell · 2024-05-28 19:42:14 UTC ·

What was traded
Price0.027118792 DGB
WHIVE amount7,508
DGB amount203.5955
≈ USD—
outside the lookback window
How long it took
Started2024-05-28 18:58:19 UTC
Finished2024-05-28 19:42:14 UTC
Took43m 55s

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 MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried for as long as that payment is unspent.

the transaction was rejected by network rules. mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation)

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 shows the maker's payment still sitting in its contract: neither claimed nor refunded. The maker had already collected the taker's payment by this step, so the taker paid and has not received the maker's coin. The secret is public, so the taker's claim can still be made; the maker can take it back after the timelock. Checked 2026-11-16 08:03:38 UTC. It will be asked again.

Wondering whether this one is yours? SwapScope cannot tell you: the parties are salted hashes, so that nobody can test a key against this data, and that cuts both ways. Search this swap's uuid in your own wallet's swap history, or open the payment transaction above on a block explorer and see whether the address paying into it is one of yours.

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

0fc9afde7ca16f0df5207432e95fd46e223d15b4caa4c53346c083f9e4fa0240

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

  • MakerPaymentReceived · MakerPaymentSent: 0fc9afde7ca16f0df5207432e95fd46e223d15b4caa4c53346c083f9e4fa0240
✓✓✓taker leg · WHIVE-segwitfrom the swap record

85e6a06a1f078e1c5c36a244b3a3bb3aa1057a36a70f2e076a3586ae872b9926

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

  • TakerFeeSent · TakerFeeValidated: 30b6f91d826ef7b3fed8c0cad40e59790ae7750253f7a061417eea0a0831aace
  • TakerPaymentSent · TakerPaymentReceived: 85e6a06a1f078e1c5c36a244b3a3bb3aa1057a36a70f2e076a3586ae872b9926
  • TakerPaymentSpent: 0da1852dda1050175dbd08e1396ef33f82ed502676bc8ed1f5e691cd6156d20c
Who traded
7cca7b82
Taker9b4c33a0
Maker clientnot reported
Taker clientnot reported
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 kdf-statsdb-8762.