fletch_

$peanut

peanut
0x04D611026C12AB86e61A5E371d18E226d09ce9d1explorer ↗
No alarms from the checks we ran. That is not a clean bill of health — it means these specific checks found nothing, and every one of them can be defeated by a contract written to defeat it.
trades on
Uniswap V3
sell simulation
unavailable
top holder
top 10
$peanut5m · 12 bars · ETH per token
first
3.561e-9
last
1.385e-9
high seen
3.150e-8
low seen
1.385e-9

change-61.10%over the bars shown

Partial history. This series begins where our index window opened2026-08-05 17:29 UTC, not at this token's first trade. Highs and lows are the extremes WE measured, never all-time.

Prices are read from the sqrtPriceX96 of indexed Uniswap V4 swaps in a single pool (0x4e80b1…c9cdf3), in ETH per token. Other venues and other pools for the same token are not blended in — an averaged cross-pool price is a number that never traded.

Index last advanced 2026-08-07 15:10 UTC.

trade

This token's pools are quoted against WETH rather than native ETH. Routing those safely needs a wrap/unwrap step we have not proven on-chain yet, so trading is turned off here rather than guessed at.

what this scan could not determine
  • Parts of the pool-discovery window could not be read, so a V4 pool may have been missed.
  • The buy/sell simulation could not be completed — the pool state we needed did not read. That is our side, not a token behaviour. Nothing is claimed either way; rescan in a minute.
  • Balance reads needed for the supply denominator did not all answer, so holder concentration was not measured rather than guessed.

These are on-chain measurements taken at 2026-08-07 15:10:51 UTC, not an audit and not advice. A token can change behaviour in the next block: liquidity can be pulled, and a contract can behave differently for you than for this simulation. We never accept payment to change what a scan says.

SYNCING