fletch_

$VC

VC
0xD65BB8E21F35aD6DAB3442480324B209ED7fe601explorer ↗
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
quoted
top holder
top 10
$VC5m · 1 bar · ETH per token
first
1.575e-9
last
1.374e-9
high seen
1.793e-9
low seen
1.374e-9

change-12.75%over the single bar

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 (0x9254be…91f2cc), 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.

2 ETH-quoted pools exist for this token; this series is one of them — prices are per pool and are not averaged.

trade $VC
1.00% fee
max slippage
simulating…

Routed through Uniswap's router on Robinhood Chain. Simulations describe this block only — a contract can behave differently in the next one. Not advice; most new tokens on this chain go to zero.

Both a simulated buy and a simulated sell returned a quote at the time of this scan.
Uniswap V3 pool 0x9254Be8D3a26fbf3BBcbF6e0A4de1FaF7791F2Cc — a buy priced from the pool's own reserves and liquidity, then the proceeds sold back into the pool as that buy leaves it, every read pinned to block 31117536 so both legs describe the same block. This says nothing about later blocks — a contract can change behaviour, and liquidity can be removed.
what this scan could not determine
  • 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-08 13:42:12 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