Robinhood Chain Explorer: the Official Blockscout URL and How to Use It

The official Robinhood Chain block explorer is https://robinhoodchain.blockscout.com, run on Blockscout and listed in Robinhood's own chain documentation. Paste any token address, wallet address or transaction hash into its search bar and it shows you what happened on the chain.

This lesson covers how to look up each of those three things, how to avoid fake explorers, and the questions the explorer cannot answer for you before you buy a token.

The official explorer, and the ones to ignore

Robinhood's documentation lists these mainnet details:

| Setting | Value |

|---|---|

| Network name | Robinhood Chain |

| Chain ID | 4663 |

| Currency | ETH |

| Block explorer | https://robinhoodchain.blockscout.com |

Type the explorer address yourself or open it from your wallet. Several third-party sites call themselves "Robinhood Chain Explorer". Some are harmless, some are not, and none of them is the one the documentation names. An explorer only needs to read data, so a page that asks you to connect a wallet or sign something just to look up an address is a reason to close the tab.

There is also a separate testnet explorer at explorer.testnet.chain.robinhood.com, for the test network with chain ID 46630. Testnet tokens have no value. If an address shows nothing on mainnet but appears on the testnet explorer, you are looking at the wrong network.

How to look up a token

1. Copy the token's contract address from a source you trust. Do not search by name: many tokens share the same ticker.
2. Paste the address into the explorer's search bar.
3. The token page shows the name, symbol, total supply and holder count.

The tabs underneath are where the useful detail lives:

• Token transfers. Every movement of the token, newest first.
• Holders. The wallets holding it, ranked by balance. Remember that the top holder is often the pool itself, not a person.
• Contract. Whether the source code is verified. A green check means the published code matches what is on the chain. If verified, you can read the code and its read-only functions here.

If the search returns several tokens with the same name, that is your warning. The copycat tickers lesson explains why it happens so often on this chain.

How to look up a wallet

Paste a wallet address into the same search bar. The address page shows:

• the ETH balance;
• the tokens it holds;
• its transactions, token transfers and internal transactions.

This is the quickest way to confirm a deposit arrived. If the explorer shows your balance and your wallet app does not, the problem is your wallet's network settings, not your funds. The MetaMask setup lesson covers that fix.

How to look up a transaction

Paste a transaction hash, the long string your wallet shows after you send or swap. Most wallets also have a "view on block explorer" link that opens it directly.

The transaction page shows:

• Status. Success or failed. A failed swap still costs gas.
• From and to. Who sent it and which contract it called.
• Token transfers. What actually moved, in which direction and how much.
• Fee. What you paid in ETH.

If a swap failed, the status line usually carries the reason. On a thin pool the most common one is that the price moved past your slippage setting before the trade landed. The slippage lesson explains what to change.

What the explorer does not tell you

The explorer is an honest record of what happened. It is not an answer to the question most traders bring to it, which is "should I worry about this token?"

Here is what it leaves for you to work out by hand:

Who bought together at the launch. The explorer lists the first buyers, but it does not tell you that ten of them were funded by the same wallet minutes before. Finding that means opening each buyer, tracing where its ETH came from, and comparing.

Whether the deployer sold. You can open the deployer's address and scroll its transfers, but the explorer will not sum up how much it bought, how much it still holds, or when it sold.

What the deployer launched before. A wallet that has launched a dozen tokens that all went to empty pools looks like any other address until you check every one of those tokens yourself.

Whether the liquidity can be pulled. You can find the pool, then find who holds its liquidity tokens, then check whether that holder is a burn address or a lock contract. Each step is a separate lookup.

Which contract is the real one. A name search returns every contract that used the name. The explorer does not rank them by where the liquidity is.

Every one of these answers is in the explorer's data. Putting them together takes many lookups per token, and a new token can move a long way in the time it takes.

Where our scanner fits

Our Robinhood Chain scanner does those lookups for you. Paste a contract at /rh and the report at /rh/scan/ followed by the address shows:

• the wallets that bought in the first blocks, which ones look coordinated, how much of the supply they took and how much they still hold;
• the launcher's own bag: what it bought and what it holds now;
• the deployer's earlier tokens and what happened to them;
• whether the pool's liquidity is burned, locked or still removable;
• whether the contract is verified on Blockscout.

Each finding links back to the evidence, so you can open the same records on the explorer and check them yourself. If a lookup could not complete, the report says unknown rather than calling it clean or calling it bad. For a wallet rather than a token, /rh/wallet/ followed by the address shows what we know about it. For a ticker, /rh/ticker/ followed by the name names the contract holding the liquidity.

Reading a Robinhood Chain scan explains each section of the report.

The short version

Use robinhoodchain.blockscout.com to confirm what happened: deposits, swaps, balances, verified code. Use a scan to answer what it means: who is bundled, whether the launcher sold, and whether the liquidity can leave. Neither one predicts a price, and neither is advice to buy.