Block Details

RHEXPLORER — every figure traces to its block

An independent explorer for Robinhood Chain. Not affiliated with Robinhood Markets, Inc. Every figure below is read from the index on this page load, never written into the page — which is the whole idea, so it starts with itself.

What this explorer gives you

• ·Provenance on every figure. Each page names the API route that produced it and the block the answer is current to. Any number here can be re-derived by the person reading it — that is the point of the thing.
• ·Labels that are derived, not assumed. A method name is proven by hashing its signature to its selector. Contract source is a bytecode match with the bytecode re-read from our own node and cross-checked, and the match type is stated. Proxies resolve to their implementation.
• ·A read interface. No accounts, no wallet connection, no transaction path. The site asks for nothing and holds nothing.

Live now

• ·Blocks, transactions, logs, transfers and approvals. Indexed to block 101,431,204 across 10,145 windows (101,431,204 blocks covered), with the chain head at 109,729,749 — 8,298,545 blocks behind.
• ·Every answer states its own completeness. Each route reports whether its answer is complete, and when it is not, the cause and the source it came from. A page will tell you it does not know something rather than imply zero.
• ·Decoded transactions. Method names are proven by selector hash, arguments are decoded from the calldata itself, and anything unproven is shown as raw hex rather than a guess.
• ·Contract source verification by bytecode match against Sourcify, with the bytecode re-read from our own node and cross-checked rather than taken on trust. Match type is always stated.

Expanding now

• ·Holder lists, token tables, internal ETH and NFT metadata are still extending across the chain. Each page states exactly how far it reaches, so you always know what a figure covers without having to track it yourself.
• ·Contract coverage is widening toward every contract on the chain. Search resolves an address, a transaction hash or a block number today; name and symbol search is indexing now.

The API — what to expect

• ·Open and keyless today. Every route this site reads is a public JSON endpoint, and the “API” link on a page shows the exact route behind it.
• ·There is a limit today, and it is plain: roughly 1 request a second for API routes with a burst of 30, and 2 a second for pages with a burst of 60, per client. Go past it and you get a 429 naming the limit with a retry-after — never a silent slowdown. Anonymous reads are being kept deliberately; most explorers have closed theirs.
• ·Not live yet: keys and cost-weighted tiers. A free self-serve key, and metering weighted by what a call actually costs rather than counted per request, because an NFT or contract call is far heavier than a block lookup. The weight table will be published next to the quota, so a request count is never quoted without it.
• ·Both per-second and per-minute limits will be published with real numbers, and a refusal will name which limit was hit and when to retry — rather than quietly slowing down, which is indistinguishable from the index being slow.

Nothing above is a release date. Every position stated here is also stated on the page that serves it, read live — this panel is a summary, never the source.