Robinhood Chain Explorers: Blockscout, RobinScan

Last updated: October 24, 2026

Endpoint and plans: Robinhood Chain RPC endpoint.

At a glance

What you see

You need to look up a transaction or a contract on Robinhood Chain and find more than one explorer, some sites with similar names, and a mainnet and a testnet explorer that do not show each other's data. Then you want the same check inside a bot or a CI job, where opening an explorer page is not an option.

Why this happens

Robinhood's connection guide names one explorer per network: robinhoodchain.blockscout.com for mainnet (chain ID 4663) and explorer.testnet.chain.robinhood.com for testnet (46630); a transaction or contract on one network never appears on the other's explorer. Robinhood's deployment guide verifies contracts through Blockscout, so verified source code and ABIs appear there. RobinScan at robin.etherscan.io describes itself as "a Block Explorer and Analytics Platform for Robinhood Chain"; independent community sites also use the RobinScan name and disclaim any link to Etherscan or Robinhood, so check the domain. Every explorer is built from the same chain data a node serves over JSON-RPC: a receipt's status, an address's code and a contract's logs are all available from standard methods, which is what automation should call. Verified source code is the exception — it is explorer data, not chain data. In the other direction, an explorer shows blocks after they are produced, while the sequencer feed that Robinhood publishes streams transactions in the order the sequencer accepts them.

Explorer or RPC: which answers what

What to do

1. Open robinhoodchain.blockscout.com for mainnet and explorer.testnet.chain.robinhood.com for testnet; if a hash is not found, check that you are on the explorer for the network you sent it on.
2. Use RobinScan only at robin.etherscan.io and treat other RobinScan-named domains as unrelated sites.
3. Verify contracts on Blockscout so their source and ABI are readable there (forge verify-contract --verifier blockscout).
4. In bots, CI and monitoring, replace explorer lookups with the RPC calls in the table: eth_getTransactionReceipt for status, eth_getCode for contract presence, eth_getLogs for events.
5. Keep RPC checks on the same network as the transaction: eth_chainId returns 0x1237 on mainnet and 0xb626 on testnet.

curl -s "$RH_RPC_URL" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionReceipt","params":["<tx_hash>"]}'
# result.status: "0x1" success, "0x0" reverted; result null: not yet included

When this is not our problem

What an explorer shows, which contracts are verified and how its pages and API behave are up to whoever runs it (Blockscout, Etherscan), not to the RPC provider behind your calls, Triport included. For automated checks on mainnet, the RPC calls above work against any Robinhood Chain endpoint; Triport's keyed form is https://triport.io/r/<YOUR_KEY>/robinhood.