fletch_

$KISMET

Kismet
0x49C62047965EafD1C0e09c4747242E9D3cBd6eB8explorer ↗
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 V4 (1 pool)
sell simulation
not run
top holder
11.3%
top 10
50.5%
$KISMET5m · 34 bars · ETH per token
first
6.155e-8
last
2.244e-8
high seen
7.510e-8
low seen
2.070e-8

change-63.53%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 (0x197cbe…860896), 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.

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

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

17.2% of supply has been sent to the burn address.
balance of 0x000000000000000000000000000000000000dEaD
what this scan could not determine
  • This token's V4 pools are not quoted against ETH/WETH, so those pools were not simulated.
  • Holder discovery covered the last 120,000 blocks (about 3.3 hours), not full history. Shown balances are verified and exact, but a wallet with no activity in that window would be missing — treat concentration as a floor.

These are on-chain measurements taken at 2026-08-08 00:11:00 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