BNB testnet explorer: check any Chapel transaction, contract or block

A BNB testnet explorer lets you inspect BNB Smart Chain’s test network, Chapel (chain ID 97), where tokens have no value and developers rehearse deployments. This one reads the testnet live: paste a transaction hash, address or block number to see status, gas, tBNB balances, token transfers and contract details, then share the result with your team.

Testnet is where every serious BSC project fails first — cheaply. Contracts revert, nonces jam, a faucet refuses you, a hash “disappears” because it was sent on the wrong network. This page pairs the explorer above with the practical knowledge around it: what Chapel is, which testnet explorers exist, where to get tBNB, how to deploy and verify a contract, how to find out why a transaction failed, and what changes when you move to mainnet. If you work on BSC mainnet most of the time, our mainnet BNB transaction explorer is the same tool with a different default network.

How to use the BNB testnet explorer

The search box and the result panel above are already set to BSC Testnet. Paste one of four things and press Enter. A transaction hash (0x plus 64 hex characters) shows status, block, gas used against the limit, the fee in tBNB, the decoded method and any BEP-20 or NFT transfers. An address shows the tBNB balance, the number of transactions sent and whether it is a contract; for token contracts it also reads name, symbol, decimals and total supply straight from the chain. A block number, or the word latest, shows the block’s validator, timestamp, gas and transactions, with buttons to step forward and back.

Data comes directly from BNB Chain’s public testnet nodes, with PublicNode as a fallback, so it is as fresh as the chain itself. One honest limitation: unlike on mainnet, there is no indexer behind testnet lookups, so address pages show live state but not a full transaction history. For that, open the same address on testnet.bscscan.com — the result page links to it. Every result has a permanent URL with &net=bsc-testnet appended, which is the quickest way to drop a failing deployment into your team chat.

What is the BNB Smart Chain testnet (Chapel)?

Chapel is the public test network of BNB Smart Chain. It runs the same client software and the same PoSA consensus as mainnet, receives hard forks first, and uses tBNB — an unlimited-supply test token with no market value — for gas. Everything you can do on mainnet you can do here: deploy contracts, mint BEP-20 tokens, test PancakeSwap-style integrations, run bots. We measured the live network while writing this guide:

You can check the same values yourself with one batched request. Like mainnet, the official testnet endpoints allow 10,000 requests per five minutes per IP and disable eth_getLogs, so plan on a provider for event-heavy tests. Our BNB Chain explorer API guide covers all the key-less endpoints and their limits.

curl -s -X POST https://bsc-testnet-dataseed.bnbchain.org \
  -H 'Content-Type: application/json' \
  -d '[{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]},
       {"jsonrpc":"2.0","id":2,"method":"eth_blockNumber","params":[]},
       {"jsonrpc":"2.0","id":3,"method":"eth_gasPrice","params":[]}]'

[{"jsonrpc":"2.0","id":1,"result":"0x61"},          # 97 = Chapel
 {"jsonrpc":"2.0","id":2,"result":"0x7ee0d3d"},     # block 133,041,469
 {"jsonrpc":"2.0","id":3,"result":"0x5f5e100"}]     # 100,000,000 wei = 0.1 gwei

To add Chapel to MetaMask or Trust Wallet, enter the values from the table as a custom network, or use the one-click buttons in our MetaMask network guide, which also covers mainnet and opBNB.

testnet.bscscan.com vs BSCTrace testnet vs this tool

Three explorers cover Chapel well, and they are good at different things.

BscScan Testnet is run by the Etherscan team and mirrors the mainnet site: verified source code, Read and Write Contract tabs, token trackers and complete address history. It is the one to use for contract verification and for anything your QA team needs to click through. Our BscScan review covers the interface in depth. BSCTrace from NodeReal has a testnet edition with the same uncluttered design as its mainnet explorer; it is the natural pick if you already use MegaNode’s testnet endpoint (bsc-testnet.nodereal.io), which is included in the free plan. Read the BSCTrace review for details. This tool is for speed: no Cloudflare check, no ads, and a result you can share in one tap.

How to get tBNB: BSC testnet faucets that work in 2026

tBNB is free, but faucets ration it to keep bots out. Two are reliable.

The official BNB Chain faucet at bnbchain.org/en/testnet-faucet sends up to 0.3 tBNB per address every 24 hours. The anti-bot rule is that the requesting address must hold at least 0.002 BNB on BSC mainnet. The same faucet also dispenses BEP-20 test tokens — BTC, BUSD, DAI, ETH, USDC, XRP and USDT — and projects that need larger amounts can apply through the BNB Chain Discord. The USDT it gives out is the test contract 0x3376…4dDd, not the mainnet one; click the “USDT faucet token” chip above to inspect it.

The QuickNode faucet at faucet.quicknode.com has no mainnet-balance requirement and no account requirement, so a brand-new wallet can claim. You get one drip per network every 12 hours; the exact amount appears after you enter your address, and sharing on X or being a paying QuickNode customer multiplies it.

Deploying and verifying a contract on the BSC testnet

Create a fresh wallet just for testing and never reuse its key on mainnet. Fund it from a faucet, then point your framework at Chapel. With Hardhat, add a network entry:

// hardhat.config.js — add Chapel next to your other networks
module.exports = {
  solidity: "0.8.24",
  networks: {
    bscTestnet: {
      url: "https://bsc-testnet-dataseed.bnbchain.org",
      chainId: 97,
      accounts: [process.env.TESTNET_DEPLOYER_KEY],   // a throwaway key, never your mainnet one
    },
  },
};

// npx hardhat run scripts/deploy.js --network bscTestnet

With Foundry, deploy from an encrypted keystore rather than pasting a private key into your shell history, then verify:

# deploy with an encrypted keystore account ("cast wallet import deployer --interactive")
forge create src/Counter.sol:Counter \
  --rpc-url https://bsc-testnet-dataseed.bnbchain.org \
  --account deployer --broadcast

# verify for free on Sourcify (supports chain 97)
forge verify-contract 0xYourContractAddress src/Counter.sol:Counter \
  --chain 97 --verifier sourcify

Verification publishes your source so that anyone, including your own front end and auditors, can read it against the deployed bytecode. You have three routes. The web form on testnet.bscscan.com is free and accepts single files, flattened source or Standard JSON input. Sourcify supports chain 97 and needs no key at all, as in the Foundry example. And Etherscan API V2 — what Hardhat’s and Foundry’s Etherscan plugins call — works with chainid=97, but Etherscan lists BSC testnet as paid-tier only, so a free key may be refused. The BNB Chain developer docs keep the current endpoint list if a URL above ever changes. After deploying, paste the contract address into the explorer above: you should see “Contract”, a bytecode size and, for tokens, the name and symbol read live.

How to debug a failed BSC testnet transaction

A transaction marked Failed was mined but reverted: the state changes were rolled back and the gas was still charged. Work through it in this order.

1. Compare gas used to the gas limit. If they are equal, the transaction ran out of gas; raise the limit or let your wallet estimate it. If gas used is far below the limit, a require, revert or custom error stopped it.

2. Get the revert reason with eth_call. Re-send the same from, to, value and data as a read-only call. The node executes it without broadcasting and returns the error string. This example simulates a transfer of the faucet USDT from an empty address:

curl -s -X POST https://bsc-testnet-dataseed.bnbchain.org \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{
        "from":"0x000000000000000000000000000000000000c0Fe",
        "to":"0x337610d27c682E347C9cD60BD4b3b107C9d34dDd",
        "data":"0xa9059cbb000000000000000000000000000000000000000000000000000000000000beef0000000000000000000000000000000000000000000000000de0b6b3a7640000"},"latest"]}'

{"error":{"code":3,"message":"execution reverted: BEP40: transfer amount exceeds balance", …}}

Yes, the testnet USDT contract really says “BEP40” — a typo baked into the deployed contract and a handy reminder that testnet tokens are separate contracts with their own quirks. One catch: public nodes keep historical state only for the most recent blocks. In our tests, a balance query about 100 blocks back worked, while 1,000 blocks back returned missing trie node. At 0.45 seconds per block that is well under ten minutes, so replay against latest or use an archive endpoint such as MegaNode’s free plan.

3. Rule out the classics. “Nonce too low” means another transaction already used that nonce; “replacement transaction underpriced” means you tried to replace a pending one without raising the gas price enough; “insufficient funds” counts gas plus value. A transaction signed for chain 97 is rejected on chain 56 and vice versa, thanks to EIP-155 replay protection — so a hash that exists on one network never shows up on the other. For token calls, check that the spender was approved first and that you used 18 decimals for the faucet tokens.

4. Step through the trace. For complex failures, simulation and tracing tools such as Tenderly and BlockSec’s Phalcon support BNB Smart Chain and show the exact call where execution reverted. Our guide to reading a BSC transaction explains every field you will see along the way.

BSC testnet vs mainnet: what actually differs

Chapel is a faithful copy of mainnet, but not an identical one, and the differences bite at launch.

Identity. Chain ID 97 instead of 56, tBNB instead of BNB, different RPC and explorer URLs. Hard-code the chain ID in your deployment scripts and assert it at start-up.

Upgrade timing. Hard forks activate on testnet first. Fermi, which cut block time from 0.75 to 0.45 seconds, reached Chapel on 10 November 2025 and mainnet on 14 January 2026. Watch testnet if you want early warning of behaviour changes.

Gas. The testnet node suggested 0.1 gwei when we checked, while mainnet’s eth_gasPrice returned the 0.05 gwei floor. Testnet blocks also had a gas limit of about 100 million, against 70 million on mainnet, so a transaction that barely fits a testnet block may need splitting on mainnet.

Addresses and liquidity. USDT, WBNB, routers and oracles all live at different addresses on testnet, and pools are thin or stale. Never copy a testnet address into mainnet config. Our BEP-20 token explorer lists the verified mainnet contracts. And because nobody’s money is at stake, testnet will not tell you how bots, MEV and real users will treat your contract.

What about the opBNB testnet?

opBNB, BNB Chain’s OP Stack layer 2, has its own testnet with chain ID 5611 (0x15eb) — we confirmed it with eth_chainId against https://opbnb-testnet-rpc.bnbchain.org. It is a different network from Chapel: to get test funds there you claim tBNB on BSC testnet and move it across with the official opBNB testnet bridge. Explorers for it are testnet.opbnbscan.com from NodeReal and opbnb-testnet.bscscan.com from the Etherscan team. Our on-site tool covers opBNB mainnet; everything about both opBNB networks and BNB Greenfield is in the opBNB and Greenfield explorer guide.

Moving from testnet to mainnet

When the tests pass, the checklist is short: switch the RPC URL and chain ID to 56, replace every testnet contract address with its mainnet counterpart, deploy from a new key that has never touched a testnet, verify the source on BscScan straight away, and fund the deployer with real BNB. That last part is cheaper than most people expect. At mainnet’s 0.05 gwei floor, a contract that takes 1.5 million gas to deploy costs about 0.000075 BNB, and a plain transfer about 0.00000105 BNB. Check live prices in the BSC gas tracker before launch, and see where your project fits among the tools in our BNB Smart Chain explorer ranking.