No aggregator serves this chain, so we index it ourselves
Robinhood Chain’s own explorer refuses our server and OpenSea’s API is gated. The public RPC answers, which is the whole reason this site exists.
MadCool Seed ·
Every NFT site you have used is reading somebody else’s index. OpenSea keeps one, Blur keeps one, the aggregators rent theirs. That is fine until the chain you want to cover is not on the list, and Robinhood Chain — an Arbitrum Orbit L2 that opened on 1 July 2026 — is not on the list.
The chain has its own Blockscout explorer, which would be the obvious place to ask. Asked from a server, it answers with a Cloudflare interactive challenge: HTTP 403, a page meant for a human with a browser. That is not a bug and it is not something to defeat; it is what an explorer does when it does not want to be somebody’s backend. OpenSea’s API, the other obvious answer, is gated behind approval we do not have.
What does answer
The chain’s public JSON-RPC endpoint answers anyone. eth_chainId returns 0x1237 — 4663 — and eth_getLogs returns Transfer events to whoever asks for them. Every NFT on this chain announced itself there when it was minted, and the record is permissionless.
The constraint did not limit what we could build. It decided what we had to build, and the thing we had to build is the only reason this site knows anything the others do not.
So we index it ourselves: a process that reads Transfer logs as blocks arrive, works out which contracts they belong to, and asks each new contract for its name and its tokenURI. It is not sophisticated. It is just nobody else’s.
What that costs, honestly
An index you run yourself starts empty. Ours began at the block we deployed it, so for its first day it knew about a day. Rather than hide that, every number drawn from it is published next to the window it covers, and a second crawl is walking backwards toward the chain’s first block to deepen it. When that crawl gives up on a range — which happens, when an endpoint refuses one long enough — the gap is recorded and listed on the chain page, because an index with a hole in it is a fact about the data and a cursor that quietly jumped is not.