MEWC/DOGE · swap

dcd89794-f087-41c3-865e-26d95991669d

Sell · 2024-03-20 23:02:54 UTC ·

What was traded
Price0.0014625598 DOGE
MEWC amount89.8818
DOGE amount0.1315
≈ USD—
outside the lookback window
How long it took
Started2024-03-20 22:56:30 UTC
Finished2024-03-20 23:02:54 UTC
Took6m 24s

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.

taker_swap:1803] utxo_common:2035] HTLC spend fee 15297022 is greater than transaction output 13145751

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:24:00 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 · DOGEfrom the swap record

731e513655f5a34cc8d31d54ed2d743748b58319c38060fd53d74661060b6abd

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

  • MakerPaymentSent · MakerPaymentReceived: 731e513655f5a34cc8d31d54ed2d743748b58319c38060fd53d74661060b6abd
✓✓✓taker leg · MEWCfrom the swap record

e0dbe1df39572a02fe1b7c6b20cf5bc8243e750a23a30055d96324a47d45193e

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

  • TakerFeeSent · TakerFeeValidated: 82638a6a6c59c8d8e3cdec6a8057e46032f391e7bf92f7974483ecb9b06d13c2
  • TakerPaymentSent · TakerPaymentReceived: e0dbe1df39572a02fe1b7c6b20cf5bc8243e750a23a30055d96324a47d45193e
  • TakerPaymentSpent: ae3695923b30be50f7df2998cacb263be58ed5c185e81811785b606feb64cee2
Who traded
616be328
Taker7f0d4258
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.