fletch_

$peanut

peanut
0x6f11DC1ae65705A82652E535519bF69a859a2B07explorer ↗
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 · 4 bars · ETH per token
first
1.123e-11
last
4.899e-11
high seen
5.094e-11
low seen
1.123e-11

change+336.31%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 (0xfd9181…647c7e), 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 22:26 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
  • The buy/sell simulation could not be completed on Uniswap V3 pool 0xFd9181Df25A578bE010A21e055a10B57b7647C7E — the tick range this measurement reads ran out before the trade could be priced. That is a limit of this measurement, not a token behaviour and not an outage. Nothing is claimed either way.
  • The buy and sell were priced from the Uniswap V3 pool's own reserves and liquidity, not by executing a swap — we could not find a Uniswap quoter deployed for Uniswap V3 on this chain. That measures whether the pool can price and pay the trade; it cannot see a restriction inside the token contract itself, such as a blocked or taxed transfer.
  • No Transfer events were seen in the scanned window, so holder concentration could not be derived.

These are on-chain measurements taken at 2026-08-07 22:26:40 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