opBNB explorer and BNB Greenfield explorers, explained

An opBNB explorer is a website that lets you inspect blocks, transactions, wallets and tokens on opBNB, BNB Chain’s OP Stack layer 2 (chain ID 204). The two full options are NodeReal’s opBNBScan and opbnb.bscscan.com; both also reveal the L2-specific data — batches posted to BSC, bridge deposits and withdrawals — that a normal BSC explorer does not have.

opBNB went live for the public on 13 September 2023 and has since become the place where games, social apps and high-frequency bots go when even BNB Smart Chain feels too busy. We sampled the public RPC while writing this: 10,000 blocks took exactly 2,500 seconds, so a new opBNB block lands every 0.25 seconds, with a 100-million gas limit and a suggested gas price of 0.001 gwei. At that pace, reading the chain well matters. This guide covers the explorers for opBNB and for BNB Greenfield, BNB Chain’s storage network, and clears up the “Boba BNB explorer” question once and for all. If you only care about the main chain, start with our ranking of BNB Smart Chain explorers.

What an opBNB block explorer shows you

At first glance an opBNB block explorer looks exactly like BscScan: a search bar, the latest blocks, a transaction list, token pages. That is no accident. opBNB is EVM-compatible, uses the same 0x address format as BNB Smart Chain and Ethereum, and runs the same kinds of contracts — BEP-20 tokens, NFTs, DEX routers. A transaction page still gives you status, from, to, value, gas used, nonce and decoded token transfers, and an address page still shows the BNB balance and token holdings.

The currency is BNB as well. Gas on opBNB is paid in BNB that was bridged over from BSC, which is why “I have BNB but can’t pay gas” is the most common opBNB support question: the BNB is sitting on the wrong chain. An explorer answers that instantly — search your address on opBNB and on BSC, and compare the balances. Our BNB transaction explorer lets you flip between mainnet, testnet and opBNB with one click for exactly that reason.

What makes a good op bnb explorer different from a plain EVM explorer is everything underneath the transaction: which BSC transaction carried it, which batch it was posted in, whether the state it produced has been proposed to BSC yet, and — for bridge users — where a deposit or withdrawal currently stands. We will get to those fields in a moment.

opBNBScan vs opbnb.bscscan.com

opBNBScan (opbnbscan.com) is built by NodeReal, the same infrastructure company behind BSCTrace and the MegaNode API. It was the reference explorer during the opBNB launch and still has the most complete layer 2 tooling. Browsing its interface you will find views for L1 State Batches, Output Root, BSC Blobs, bridge Deposits and Withdrawals, daily deposit and withdrawal statistics, contract verification and address-ownership verification. Transaction pages split the fee into the L2 execution cost and the L1 fee, following the formula it prints right on the page: “Txn Fee = Gas Price × Gas + L1 Fee”. If you like NodeReal’s cleaner style on the main chain, read our BSCTrace review — opBNBScan is its layer 2 sibling.

opbnb.bscscan.com is the Etherscan team’s version. It looks and behaves like BscScan for opBNB: familiar menus, verified contract Read/Write tabs, labels, token pages and the same Cloudflare bot check. For developers it has one very practical advantage — opBNB (chain 204) is still covered by the free tier of Etherscan API V2, while BNB Smart Chain mainnet is not. Our explorer API guide explains that split in detail.

Both full explorers read the same chain, so balances and transaction results always match. The choice comes down to what you need next: opBNBScan when you care about the rollup mechanics, opbnb.bscscan.com when you want the BscScan workflow you already know.

What is different on a layer 2 explorer?

opBNB is an optimistic rollup. A single sequencer — currently operated by the opBNB team, as BNB Chain’s own FAQ states — orders transactions and produces L2 blocks. The raw transaction data is then compressed and posted to BNB Smart Chain in batches, and a proposer periodically publishes a commitment to the new L2 state. Security comes from the fact that anyone can re-derive opBNB’s state from what is on BSC and challenge a wrong commitment during the challenge window. Every one of those steps leaves a trace an opBNB explorer can show you.

L1 fee and batch data

Because opBNB pays BSC to store its data, each L2 transaction carries an L1 fee on top of the normal gas cost. On explorers you will see it as a separate line, often with the L1 gas price and the fee scalar used. The batch view shows which BSC transaction carried a group of L2 blocks. opBNBScan also has a BSC Blobs section: BSC supports blob-carrying transactions (the EIP-4844 design borrowed from Ethereum), which let a rollup post data far more cheaply than ordinary calldata, and the explorer displays blob size, blob gas price and the sender.

State batches and output roots

An output root is a hash that summarises opBNB’s state at a given L2 block. The proposer submits these roots to a contract on BSC, and opBNBScan lists them as L1 State Batches with the BSC transaction hash. Why should you care? Because a withdrawal can only be proven once an output root covering its L2 block has been posted. If your withdrawal is stuck at “waiting for proof”, the state-batch list tells you whether the root you need exists yet.

“Latest” is not the same as “finalized”

BNB Chain’s FAQ points out that opBNB’s finalized block height typically trails the latest block by more than 200 blocks — a direct consequence of the OP Stack design, where an L2 block becomes final once its data is safely included and finalized on BSC. For payments on opBNB itself, the sequencer’s confirmation is usually all you need in practice. For large bridge movements and exchange credits, finality on the L1 side is what counts, and a good explorer lets you check both.

Tracking deposits and withdrawals through the opBNB bridge

The official bridge lives at opbnb-bridge.bnbchain.org. Moving funds from BSC to opBNB is a deposit: you send one transaction on BSC, the bridge contracts emit an event, and the sequencer includes a matching deposit transaction on opBNB, usually within a few minutes. On opBNBScan, the L2 side of a deposit links back to its L1 Deposit Txn on BSC, so you can prove both halves. If the BSC transaction is confirmed but nothing has appeared on opBNB after a reasonable wait, search your address on opBNB before assuming the worst — deposits often arrive while the wallet UI is still catching up.

Moving funds from opBNB back to BSC is a withdrawal, and it is deliberately slow. According to the official opBNB withdrawal guide it takes three actions:

1. Submit the withdrawal on opBNB. The bridge shows the status “Waiting for Proof”.
2. Submit the proof on BSC — manually, once an output root covering your withdrawal has been posted.
3. Claim your tokens on BSC after the 7-day challenge period has passed.

Each step is its own transaction, so you end up with three hashes: one on opBNB and two on BSC. Keep all three. On opBNBScan the withdrawal record shows the L1 Withdraw Txn Hash; on the BSC side you can paste the prove and claim hashes into any BSC explorer. The seven days are not a bug or a backlog. They are the window in which anyone can dispute an invalid state commitment, and they are what makes the official bridge trust-minimised. The testnet window is shorter, which is why developers rehearse there first.

If you cannot wait a week, third-party bridges offer faster exits by fronting liquidity or using other proof systems. BNB Chain itself warns that community bridges may not be as secure as the official one, so treat them as a trade-off, not a free upgrade.

opBNB testnet explorers

The opBNB testnet runs on chain ID 5611 and settles to the BSC testnet (Chapel, chain ID 97). Both explorer families have a testnet edition: testnet.opbnbscan.com from NodeReal and opbnb-testnet.bscscan.com from the Etherscan team. The testnet bridge sits at opbnb-testnet-bridge.bnbchain.org, and its shorter challenge window lets you walk through a complete deposit–prove–claim cycle in a single session.

You will need testnet BNB on Chapel first, then bridge it over. Our BNB testnet explorer guide lists the faucets and the usual pitfalls, and the MetaMask network setup page gives you the RPC URLs and block explorer URLs for BSC, Chapel and opBNB so your wallet opens the right explorer on every click. Deploying contracts? Verify them on both explorers — users check whichever one their wallet links to.

BNB Greenfield explorer: GreenfieldScan

BNB Greenfield is a different animal. It is not an EVM rollup but a storage-focused blockchain that launched its mainnet on 17 October 2023. The chain keeps the metadata and permissions for files; the files themselves are stored off-chain by independent storage providers. Accounts still use familiar 0x addresses, and BNB pays for transactions and storage. Its chain identifier is greenfield_1017-1, and blocks arrive about every 2.5 seconds on the explorer’s dashboard.

The concepts you will meet on a bnb greenfield explorer map to cloud storage terms:

• Buckets are containers, like folders at the top level of an S3 account. Each has an owner, a primary storage provider and a visibility setting.
• Objects are the files inside a bucket. Creating an object is a two-step process you can watch on-chain: a Create Object transaction registers it, then a Seal Object transaction confirms the storage provider has actually stored the data.
• Groups bundle accounts so a bucket or object can be shared with many people at once.
• Storage providers (SPs) are the infrastructure operators that hold the data, work alongside Greenfield validators and get paid through storage payment streams.
• Validators and proposals run consensus and on-chain governance, as on any Cosmos-style chain.

GreenfieldScan, powered by NodeReal, is the explorer for all of this. Its menus cover Blockchain, Storage, Validators, Proposals, Parameters, Chain Info and Statistics. The homepage shows the latest block, total transactions and addresses, daily stored data and total network storage, plus live feeds of newly created buckets and objects. Click into a bucket to see its creator, active object count and the transaction that created it. If you just want to upload or download files, DCellar — linked from GreenfieldScan’s header — is the user-facing storage app; GreenfieldScan is where you verify what happened. The BNB Greenfield documentation goes deeper into permissions, cross-chain programmability with BSC and billing.

What happened to the Boba BNB explorer?

People still search for a “boba bnb explorer”, so here is the straight answer. BobaBNB was Boba Network’s optimistic rollup for BNB Chain, launched in November 2022 and marketed at the time as the first layer 2 on BNB Chain. It ran on chain ID 56288 with BOBA as its gas token and had its own block explorer.

On 15 September 2025 the Boba Governance Foundation announced that BobaBNB was being shut down, citing BNB Chain changes that made it incompatible with the OP Stack, and asked users to move all funds out before 15 October 2025 or risk losing access to them. When we checked in September 2026, the BobaBNB public RPC and block explorer domains no longer resolved. Chain lists such as ChainList may still show chain 56288, but that is a leftover entry, not a sign the network is alive.

If you still see BobaBNB tokens in an old portfolio tracker, that is cached data. And if anyone contacts you offering to “recover” funds from BobaBNB for a fee, treat it as a scam. For layer 2 activity on BNB Chain today, opBNB is the network to follow and opBNBScan or opbnb.bscscan.com are the explorers to use.

Which explorer should you open?

For a quick answer to “did it arrive?”, use the lookup at the top of this page with opBNB selected — it is fast, needs no login and produces a link the other side can open. For bridge problems, go to opBNBScan: the deposit, withdrawal and state-batch views are where stuck transfers get explained. For verified contract source, labels and the BscScan workflow, open opbnb.bscscan.com. For anything involving files, buckets or storage providers, it is GreenfieldScan.

Two habits save most headaches. First, always check the network before the transaction: the same wallet address exists on BSC, opBNB and the testnets with different balances, and a hash exists on only one of them. Second, never connect your wallet or sign anything on an “explorer” — real explorers only read public data. If you run your own infrastructure instead, compare the options in our Blockscout on BNB Smart Chain guide, and when the main-chain explorers are slow, the BscScan alternatives page lists backups that read the same data. Curious where BNB Chain’s other retired chain went? Our BNB Beacon Chain explorer page covers the BEP-2 era and token recovery.