fletch_

$SilverCoin

SilverCoin
0xb0b1CD5a69c51c593B465957652DE420c212CBE0explorer ↗
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
none in scanned window
sell simulation
not run
top holder
top 10
$SilverCoin5m · 7 bars · ETH per token
first
2.260e-11
last
1.851e-10
high seen
4.358e-10
low seen
2.260e-11

change+718.84%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 (0x716858…6b167a), 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 09:25 UTC.

trade $SilverCoin
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.

what this scan could not determine
  • Parts of the pool-discovery window could not be read, so a V4 pool may have been missed.
  • No V2 or V3 pool exists, and no V4 pool was seen — but parts of the scan window were unreadable, so this is a blind spot, not a finding.
  • No Uniswap pool was found to simulate a buy or a sell against, so the trade simulation did not run.
  • 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 09:25:47 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