fletch_

$ROAR

Roaring Cat
0x90B0A47af922A0E1aa38D5D2d108D80bab5dCc17explorer ↗
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
$ROAR5m · no data

No swaps for this token were indexed in the window we queried — from 2026-08-06 12:47 UTC to now. That is a fact about the window, not about the token: it may have traded before that, before the index started, or on a venue this walker does not cover.

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, 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 12:47 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.

Both a simulated buy and a simulated sell returned a quote at the time of this scan.
Uniswap V3 pool 0x0F6b1362Cb1eEf5F18b5Adb230465c796b2d543D — 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 30222423 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-07 12:47:32 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