Reading HoodStalk

There is one search box and it takes three kinds of input. It decides where to send you by the shape of what you paste, so there is nothing to choose first.

Anything else is refused with a hint rather than a guess. Token symbols and ENS names are not resolved.

A wallet page opens with the identity block — the address, whether it is a contract, and whether that contract's source has been verified — followed by the balance in ETH and its worth in dollars.

Below that sit the token holdings, then the transaction history, newest first. History arrives progressively: the page renders the first batch as soon as it lands and keeps walking backwards while you read, up to 600 transactions. Wallets busier than that are truncated, and the full record stays available on Blockscout.

The page is assembled from three independent reads. If the indexer is down but the node answers, you still get a balance — a partial page rather than an error.

Every token on the front page opens its own page: price, market capitalisation, 24-hour volume, total supply, holder count, and the number of transfers it has ever recorded.

Under that sit the largest holders, each with its share of supply, and the most recent transfers. Holders are frequently contracts rather than people — pools, vaults, and multisigs — and are named where the chain knows the name.

Paste a token's contract address into the search and you will land on its address page, since nothing in the shape of an address says it is a token. That page links across to the token view once it recognises one.

A transaction page states whether it confirmed, failed, or is still pending, then the value moved, the fee paid, the gas bought against the gas actually burned, and both parties to it.

Calldata is shown raw. When a transaction carries no calldata it was a plain transfer; when it carries a great deal, it was a contract call, and the first four bytes name the function.

Every wallet, token and transaction page has an assistant attached to it. It is handed the record for that subject before you ask anything, and it answers from that record alone — balances, counterparties, timing, patterns in the history in front of it.

It cannot see other pages, it does not browse, and it has no opinion on price. Asked something the record does not answer, it says so instead of inventing a figure.

The list on the front page is Robinhood's own tokenised equities and ETFs — the ones it issues under the name <Asset> Robinhood Token. They are ranked by market capitalisation and the suffix is trimmed for reading.

Plenty of other tokens are bridged onto Robinhood Chain and several are far larger. They are deliberately left out; this site is about what Robinhood put on its own chain.

Two public sources, and nothing else. Indexed data — histories, holdings, counters, token metadata — is read from the chain's Blockscout instance. Anything a node can answer directly, such as a live balance or a transaction by hash, is read over JSON-RPC.

The node calls pass through this site's own endpoint so the provider key stays on the server; the indexed calls go straight from your browser. No figure on this site is entered by hand, and none of it is privileged.

Results are held briefly in memory, so returning to a page you just left costs nothing. Live panels re-read every 30 seconds, and stop entirely while the tab is in the background.

For node endpoints, bridging, and everything to do with the chain itself rather than this explorer, see the official Robinhood Chain documentation.

HoodStalk only reads. There is no wallet to connect, nothing to sign, and no transaction you can send from here. It holds no account of yours because it has no accounts.

It also does not render block pages, resolve names to addresses, or chart anything. For those, Blockscout is one click away on every hash.