$MANCER

reading this pool's swap logs…

• · We could not read $MANCER's metadata getters just now. So nothing is shown above rather than an empty list — an empty list would read as “this token publishes nothing”, which is a claim about the token made out of our own failed read.
• · Read them yourself: the contract on the explorer ↗

• · V4 depth is UNMEASURED, not zero: V4's PoolManager is a singleton holding every pool's tokens in one contract balance, so per-pool reserves cannot be read as balances. We say so rather than guess.
• · “unread” rows are OUR RPC failing at snapshot time — a fact about our read, never a statement about the pool.
• · Volume is the 24h ETH leg the chainwide index attributed to each pool — a floor over what its per-tick budget could walk, never a lifetime total. Share divides by $MANCER's 24h ETH across all 54 of its pools, not just the rows listed.

• · Every row is the account that SIGNED the swap transaction — never the router the trade was routed through. (Measured while building this: every swap-event “sender” in a live window was a contract; a board of those would be a list of routers.)
• · Totals cover ONLY the indexed window: 7,183 swaps attributed for $MANCER between 2026-08-07 00:37Z and 2026-08-07 08:13Z — at least 26% of the 26,926 swaps our volume index counted over the same hours. Attribution is budgeted per tick and takes the highest-value blocks first, so every figure here is a floor over a stated period, never a lifetime total.
• · ETH in and ETH out are shown separately because net alone cannot tell “never sold” from “round-tripped”.
• · An account signing on others' behalf (a keeper, a relayer) appears as one signer. The “tokens” column is shown so bot- and infrastructure-shaped accounts are visible rather than silently ranked as people.

last 24h 7.228 ETH added over 10 events · 7.793 ETH left the pools over 8 movements (V3 collects and V2 burns — the two ways tokens actually leave a pool contract) · 7 V3 positions closed, crediting 7.762 ETH of principal. A V3 burn moves nothing; the collect that pays it out is already in the figure above when it happened inside this window, and has not happened yet when it did not. Either way it must not be added · 36 V4 events carry a liquidity delta and no amounts, so they are counted here and add nothing to the ETH figures. Floors over the pools and blocks we walked, not a census.

We could not measure holder distribution for $MANCER: our node did not answer, so no holder read was attempted. Nothing is claimed about this token's distribution. No percentage is shown, because a failed read of ours must never render as a number about someone else's token.