reading this token's identity and market
reading this token's identity and market
Ticker, name and decimals come from the index's read of the contract. Any token can claim any name, including one already in use by another: eight different addresses on this chain answer “RedBull”. Nothing here is a check on who wrote it — that is what the safety scan is for.
$JPYC price, 1 5m bar, ETH per token. Opens 0.0₇2320 at 2026-08-06 15:10 UTC, closes 0.0₇2320 at 2026-08-06 15:10 UTC. Highest measured 0.0₇2320, lowest measured 0.0₇2320. Partial history: the series begins where the index window opened, not at this token's first trade.
Partial history. This series begins where our index window opened — 2026-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 from indexed Uniswap swaps in a single pool (0xa2fba4…c1f135), in ETH per token. Prices are per pool, never averaged — an averaged cross-pool price is a number that never traded anywhere.
Quiet spans render as gaps: a missing bar means no swap with a derivable price was indexed for that bucket on this pool. Bars are never interpolated. Volume bars are the ETH leg of the indexed swaps in each bucket.
Index last advanced 2026-08-07 11:51 UTC.
showingthe busiest of this token's pools, chosen for you — the default pick
chart pool: the busiest pool, chosen for youreading this token's pools…
reading this pool's swap logs…
Volume is the ETH leg of Uniswap V2, V3 and V4 swaps indexed since the disclosed start time — a floor, not an all-time figure. Age is when we first saw a POOL, not when the token was created. Holders are not counted here; they are measured on the scan, where the exclusion rules are stated. Tokens on this board are not endorsed, reviewed or affiliated, most new tokens on this chain go to zero, and nothing here is advice.
reading what the token contract publishes about itself…
reading the trader index…
reading the pool index and snapshotting depth…
walking Transfer logs to nominate wallets, then reading their balances…
reading the liquidity-event index…
reading this pool's swap logs…
| V3 0xa2fb…f135 | 1.00% | 5.00e-6 ETH |
24h ETH leg per pool. “n/a” is a pool with no ETH side — its swaps are counted, and no ETH figure is invented for it. The chart and the tape open on the single pool with the most indexed swaps; prices are per pool and are never averaged.
No swaps have been attributed to a signer for $JPYC yet. Trader attribution covers only the window since it was switched on, and only what its per-tick budget could read — so this is a statement about our coverage, not about whether anyone is trading. The chart and volume above come from a separate, older measurement.
written by the token contract · unverified · not fletch's words
no description published
links — unread
last 24h 0 ETH added over 0 events · 0 ETH left the pools over 0 movements (V3 collects and V2 burns — the two ways tokens actually leave a pool contract). Floors over the pools and blocks we walked, not a census.
No liquidity event has been indexed for $JPYC. We have walked none of its pools, so this is not a measurement of anything.
| pool | fee | age | vol 24h | share | depth |
|---|---|---|---|---|---|
| V3 0xa2fb…f135 ◆ charted | 1.00% | 20h | 5.00e-6 ETH | 100% | unread |
No holder concentration is shown for $JPYC: no Transfer events appear in the window we walked, and the token emitted no logs at all in the blocks we probed to check — so it looks quiet rather than clipped. No wallet could be nominated for a balance read.
· The read itself worked — this is what it found, not an outage. Candidate discovery covers the last 120,000 blocks (about 3.3 hours) of chain history, so a token whose transfers all predate that window is invisible to it.