On Robinhood Chain a token is identified by its contract address. Robinhood publishes the official addresses on its contracts page and in its asset registry API, and the Blockscout explorer shows what the chain recorded about that contract: the creator, the creating transaction, the holders and whether the source code is verified.
The explorer and the status page
The explorer is named in the connection table of the documentation: "Block Explorer | robinhoodchain.blockscout.com" for mainnet and "explorer.testnet.chain.robinhood.com" for testnet, in the same table as "Chain ID | 4663 | 46630". A token page is the explorer address plus /token/ and the contract address; the same contract also has an address page under /address/.
The state of the network itself is a different surface: the status page at status.robinhoodchain.offchain.io keeps the uptime and the incident history.
Official addresses: the contracts page
The addresses come from Robinhood, not from the explorer. The token contracts page opens with "The following contracts are deployed on Robinhood Chain" and prints two of them statically: WETH at 0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73 and USDG at 0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168.
Below them sits the section for Stock Tokens and tokenized ETFs, whose table, in the page's own words, "is generated live from the on-chain asset registry". The same registry is served as an API, documented on the Stock Token APIs page: GET https://api.robinhood.com/rhj/assets returns "Asset metadata for Stock Tokens, including the current corporate-action multiplier and per-chain deployments". Each entry carries the ticker, the token name, the status and the deployment with chain ID 4663.
What Blockscout shows about a token
Read on 17 September 2026 on the pages of USDG and of a meme token on the chain. A token page carries four tabs — Details, Contract, Token transfers, Holders — and the Details tab shows Price, Circulating market cap, Total supply, Holders, Transfers and Decimals. Next to the name stand the standard badge, ERC-20 for both, and a link to the address page.
The address page records the deployment: Token name, Creator, the creating transaction under the label "at txn", and Implementation when the contract is a proxy, plus the counters Transactions, Transfers and Gas used. Open the creating transaction and the explorer gives its timestamp in three forms — Local, UTC and Unix — with the block and batch numbers and the state on Ethereum.
Creator is the address that deployed the contract, and not always a person’s. On the USDG page the creator matches the sender of the creating transaction. For the meme token it does not: the transaction reads "Interacted with contract LongLauncher", so the token was deployed by a launchpad factory.
Verification lives on the Contract tab. For USDG it reads "Contract source code verified (exact match)" and "This contract has been verified using Blockscout Bytecode Database", with the contract name, the compiler version, the optimizer settings, the "Verified at" date and the path of the source file. The explorer also reports when a contract is a proxy and by which standard: EIP-1967 Transparent Proxy for USDG, EIP-1167 Minimal Proxy for the meme token, whose creation code still carried a "Verify & publish" button.
Same ticker, different contract
A ticker is a string inside a contract, and the explorer lists what is deployed, not what is official. Among the first rows of the explorer's token list for NVDA on 17 September 2026 stood at least four tokens whose name reads exactly "NVIDIA • Robinhood Token (NVDA)", at different addresses, and the list did not end there. One of those addresses was in the asset registry: 0xd0601CE157Db5bdC3162BbaC2a2C8aF5320D9EEC.
That is the case the contracts page describes: "Use the addresses on this page to identify the canonical Robinhood Stock Token for each underlying — a token with a matching name/ticker but a different contract address is not a Robinhood Stock Token."
Missing from the registry is not the same as pretending to be in it. In our stock-paired map the token AI at 0x2e8c31162b855a2ffa90f6f8634643ad6f111e18 is a meme token that trades against the NVDA Stock Token: the registry holds the second address, not the first. Which meme tokens on the chain are paired with which stock: meme coins on Robinhood Chain.
Stock Tokens
A Stock Token is, in the documentation's words, "a standard ERC-20 contract with 18 decimals", issued by Robinhood Assets (Jersey) Limited, and its address is checked against the contracts page and the asset registry, not against the name in the explorer. The product is closed to investors in a list of jurisdictions that includes Russia, Belarus and Ukraine, and the restricted jurisdictions page notes that the list "may be subject to change".
What the chain's own token is, and what it is not: the token and airdrop question. How the product is built, from the tokenisation window to the multiplier: Robinhood Stock Tokens.
Checklist
- Take the address from the source: the token contracts page for WETH and USDG, the same page or
api.robinhood.com/rhj/assetsfor a Stock Token. - Open
robinhoodchain.blockscout.com/token/with that address and compare the address in the header with the one you copied, character by character. The name in the header is not the check. - On the address page read Creator, the creating transaction with its timestamp, and Implementation if the contract is a proxy.
- On the Contract tab read the verification line and, for a proxy, which contract the implementation points to.
- A token bridged from Ethereum has a different address here: the Robinhood Chain bridge.
Chain ID, the explorer, the ecosystem list and the exchange routes into the network are on the Robinhood Chain hub.