Bridged on Robinhood Chain

PEPEPepe

Pepe trades on Robinhood Chain as the token PEPE, deployed at the contract address below. Robinhood lists it at its public asset endpoint and Fletch found bytecode at that address on chain. A watcher on it messages your Telegram when a transfer clears a threshold you set.

confirmed on chain

The contract answers with the symbol and decimals Robinhood published.

contract answers: Pepe · PEPE · 18 decimals

contract address

0xeeba1996dad6d981bd90e812196b40d555eaa9eb

Opens on Blockscout, the chain's explorer.

Alert me when PEPE is paused, halted, split or its feed goes stale · changelog for PEPE

Watching needs a wallet sign-in and a Telegram link, once. Free during the beta.

Live state

contract read 2 min ago
Supply
1,497,166.21totalSupply()

Supply reconciliation, 2026-09-04

Contract says 1,497,166.21. Minted 0.00, burned 0.00 since the first block. Residual 1,497,166.21.

Latest mints and burns

Holders and activity

Running balances from every PEPE transfer the ledger has applied, and each day's transfers as economics: how many settled against USDG in the same transaction, how many happened outside US market hours. The ledger is still reading history: block 1,869,499 of 54,316,216. Figures below are partial until it reaches the head. Holders as JSON, activity as JSON.

holders
0
largest holder
top ten
gini
issuer wallet
HolderBalanceShare
No balances applied yet.
DayTransfersVolumevs USDGOff-hours
No days recorded yet.

Lookalike tokens

Other ERC-20s on Robinhood Chain that use the ticker PEPE or this token's exact name. The only PEPE the issuer stands behind is 0xeeba19…eaa9eb; a contract counts as issuer-deployed only when its beacon slot points at the registry. Found through Blockscout's search, settled by a storage read, refreshed every six hours. Every lookalike on the chain.

TokenAddressHoldersVerdict
PEPETHE CHOSEN FROG0x36a276…36631331,947not the Arbitrum bridge's
PEPETHE CHOSEN FROG0x9b09c4…ed4eb91,572not the Arbitrum bridge's
PEPEPepe By Matt Furie0xc79234…4204501,343not the Arbitrum bridge's
PEPEMogCat0x43cdf6…327c2b1,120not the Arbitrum bridge's
PEPEPepe The Cat0x4e069e…66b09a1,116not the Arbitrum bridge's
PEPEPEPE THE FROG0xb641d2…02aa851,086not the Arbitrum bridge's
PEPEPepecoin0x1320d2…6c30961,011not the Arbitrum bridge's
PEPEPepe in Hood0x22d7f6…0ab4031,011not the Arbitrum bridge's
PEPEPepe in Hood0xcdcabf…7f08f01,011not the Arbitrum bridge's
PepePepe le Pew0x8d5add…e34e951,002not the Arbitrum bridge's
PEPE⁠PEPE0x265824…4ced931,001not the Arbitrum bridge's
PepePepe0x0e6774…4ef4671,000not the Arbitrum bridge's
PEPEPepe The Cat0x6833c7…fbdae3791not the Arbitrum bridge's
PEPERobinhood PEPE0x6968e5…9e1b10769not the Arbitrum bridge's
PepePepe le Pew0xff91f8…dddd9c677not the Arbitrum bridge's
PEPEPEPE0x00642b…52834b569not the Arbitrum bridge's
PepePepe the corgi0x65a962…bc22d4409not the Arbitrum bridge's
PEPEPepeWifHood0xa4bd8d…437a88351not the Arbitrum bridge's
PEPEPepe Community0x2ea054…a6fecb22not the Arbitrum bridge's

Largest recent transfers

Transfer events for PEPE in blocks 54314801 to 54316301, largest first.

No PEPE transfers in the last 1,500 blocks.

How Fletch verifies PEPE

The address comes from Robinhood's asset endpoint. Every fifteen minutes Fletch asks the chain for the bytecode at that address, and weekly it asks the contract for its own name, symbol and decimals. A row reads confirmed only when the contract answers with what Robinhood published. That is a check on identity, not an audit of what the contract does.

https://api.robinhood.com/rhj/assets

What an alert on PEPE does

A watcher reads each new block on Robinhood Chain and compares every PEPE transfer against your threshold. When one clears it, you get a Telegram message with the amount, the two addresses, and a link to the transaction. Alerts are sequencer-confirmed, which is the chain's own confirmation, and they are withdrawn if a reorg removes the block.

All tokens on Robinhood Chain