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 is
·Completeness is part of the answer. Block lists, transaction lists, logs, address history and the coverage map each state whether the answer is whole, and name the cause and the source when it is not. You can quote a page here and know what you are quoting. Most explorers return an answer and leave you to assume it is complete. Single-block and single-transaction coverage statements arrive in the next index release.
·Nothing is guessed. A method name is proven by hashing its signature to the selector, or shown as raw hex. A contract is verified by bytecode match with the bytecode re-read from our own node and cross-checked, and the match type is stated. An unverified contract is a confirmed negative, not a blank.
·Read-only by design — nothing to sign. No accounts, no wallet connect, no write path, no transaction this site can ask you to approve. Write functions on a contract are listed and deliberately not callable. There is nothing here to phish and nothing to connect.
Live now
·Blocks, transactions, logs, transfers and approvals. Indexed to block 77,709,279 across 7,772 windows (77,709,261 blocks covered). The independent head probe is 10s old and currently reads at or below the newest indexed block, so the distance to the chain head is not established on this page load rather than shown as zero.
·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.
Still filling in
·Some datasets are still catching up — holder lists and token tables lag, internal ETH is proven for part of the chain, and per-token NFT metadata is built and not yet serving. You do not have to remember any of that: each page says it where the value would be, with the cause.
·Contract coverage is widening toward every contract on the chain, and name and symbol search is still indexing, so the search box resolves an address, a transaction hash or a block number.
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. Everything still filling in is already visible as incomplete in the answers themselves — you will never have to take this panel's word for it.
Reopen any time from “Build status”, bottom right.