This BNB transaction explorer is a free lookup for BNB Smart Chain. Paste a transaction hash to see whether a payment succeeded, how much it cost and which tokens moved; paste an address to see its balance and holdings; paste a block number to see what was inside. Every result can be shared as proof of payment.
It exists because most of the time you do not need a full-blown block explorer. You need one answer — “did the money arrive?” — and you need it on your phone, in a few seconds, without ads, pop-ups or a Cloudflare check. If you want the bigger picture of which explorer to use for what, our ranking of BNB Smart Chain explorers compares BscScan, BSCTrace, OKX Explorer and the rest.
How to use the BNB transaction explorer
The search bar accepts four kinds of input and figures out which one you gave it. There is nothing to configure beyond the network switch above the results.
- 1
Copy what you want to check
A transaction hash (0x + 64 hex characters), a wallet or contract address (0x + 40), or a block number. Wallets usually hide the hash behind “View details” or “Copy transaction ID”.
- 2
Pick the network
Leave it on BSC Mainnet for normal payments. Switch to BSC Testnet or opBNB if the transaction happened there — the same hash does not exist on two chains.
- 3
Paste and search
Drop the value into the search bar and press Enter. The tool detects the type automatically and reads the chain live, usually in under two seconds.
- 4
Read the result
Start with the status badge, then the amount, fee and confirmations. Scroll to Token transfers to see which BEP-20 tokens actually moved.
- 5
Share or save the proof
Use Share, Copy link or Copy payment receipt to send a verifiable record to the other side — no screenshots needed.
Transaction hash (tx ID). A 66-character string starting with 0x. Every wallet shows it after you send something: in MetaMask it sits under “Activity → transaction → Copy transaction ID”, in Trust Wallet under “Transaction details”, and exchanges usually label it “TxID” in the withdrawal history. It is the only identifier that points to exactly one transfer, so it is what support teams ask for.
Wallet address. A 42-character 0x… string. The same address format is used on Ethereum, BSC and opBNB, which is why people so often look in the wrong place. The tool reads the balance on the network you selected.
Token contract. Also a 42-character address, but one that holds code. The tool notices this, reads the token name, symbol, decimals and supply, and runs a quick security scan. Try the “USDT (BEP-20) contract” chip above: it opens the real Tether contract on BSC, 0x55d3…7955.
Block number. Any whole number, or the word latest. Handy when a payment processor says “confirmed in block 123,772,659” and you want to see the block for yourself.
What every field in a BSC transaction result means
A transaction result is built from three node calls — the transaction itself, its receipt and the block it landed in — plus token metadata. Here is how to read each part, top to bottom.
| Field | What it tells you | Watch out for |
|---|---|---|
| Status | Success, Failed or Pending | Failed still costs gas |
| Amount | BNB sent, or the main token transfer | Check the token symbol |
| Transaction fee | Gas used × gas price, in BNB and USD | Tiny on BSC: fractions of a cent |
| Confirmations | Blocks built on top since inclusion | Grows ~2 per second |
| Method | Decoded function, e.g. transfer | “Unknown” = unlisted selector |
| Gas used / limit | Work done vs. maximum allowed | 100% used often means a revert |
| Nonce · Tx type | Sender’s tx counter; 0 legacy, 2 EIP-1559 | Gaps cause stuck transactions |
Status, block and timestamp
Success means a validator included the transaction and every instruction ran. Failed means it was included but reverted — maybe slippage was exceeded on PancakeSwap, maybe the token blocked the transfer. The fee is paid either way, because validators did the work; the value and token transfers simply did not happen. Pending means the node knows about the transaction but no block contains it yet. Since the Fermi upgrade blocks arrive roughly every 0.45 seconds, so anything pending for more than a few seconds deserves a look at the gas price and nonce. The timestamp is the block time in your local time zone, with a relative “x minutes ago” beside it.
From, To and “Contract created”
From is always the wallet that signed and paid for the transaction. To is trickier: for a plain BNB transfer it is the recipient, but for a token transfer it is the token contract, not the person receiving tokens. The real recipient of USDT, CAKE or any other BEP-20 token is shown in the token transfers table. If the transaction deployed a new contract, the row changes to “Contract created” and shows the new address.
Value, fee and gas price
Value is the native BNB attached to the transaction — zero for most token transfers. The transaction fee is gas used multiplied by the effective gas price, shown in BNB and converted to dollars at the live rate. The gas price is displayed in gwei (one billionth of a BNB). On BNB Smart Chain the network floor is 0.05 gwei, so a plain BNB transfer of 21,000 gas costs about 0.00000105 BNB. Our sample USDT transfer used 34,515 gas at 0.1 gwei — roughly 0.0000035 BNB. If you want to know whether you overpaid, compare with the live BSC gas tracker.
Method, events and token transfers
The method is the contract function that was called, decoded from the first four bytes of the input data. A built-in dictionary covers the common ones — transfer, approve, swaps and liquidity calls — and anything else is looked up in the public OpenChain signature database. Next to it you may see a count of swaps and approvals detected in the logs. The token transfers table lists every BEP-20 and NFT movement decoded from the standard Transfer event, with symbols and decimals read from each token contract. This is the part that answers “what did I actually receive?”. For a field-by-field walkthrough with failed and internal transactions, read how to read a BSC transaction.
Gas used, nonce and event logs
Gas used / limit compares the work the transaction consumed to the maximum the sender allowed. A failed transaction that used 100% of its limit ran out of gas; one that stopped far below usually hit a require check. The nonce is the sender’s transaction counter — each new transaction must use the next number, which is why a stuck low-nonce transaction blocks everything behind it. Event logs is the raw count of events emitted; a simple transfer emits one, a multi-hop swap can emit dozens.
Wallet and token contract results
Paste an address and the tool first asks the node three questions: what is the BNB balance, how many transactions has it sent (the nonce) and does it hold code. The answers produce the header of the result — BNB balance, Transactions sent, Account type (wallet or contract) and, for contracts, Bytecode size.
On mainnet the tool then adds token holdings, recent BNB transactions and recent token transfers from the Binplorer index. Holdings are sorted by dollar value. We deliberately ignore price quotes for tokens with less than $50,000 of daily trading volume, because spam airdrops often carry absurd prices that would make any wallet look like a millionaire’s. So if an unknown token shows no value, that is a feature, not a bug. To go deeper — approvals, alerts, whale watching — follow our guide to tracking a BNB wallet.
When the address is a token contract, you also get Token details (name, symbol, decimals, total supply) and a Quick security scan by GoPlus: honeypot flag, buy and sell tax, whether the source is verified, whether it is mintable or an upgradeable proxy, holder count, blacklist functions and whether the owner can change balances. A red flag here is a reason to stop; a clean scan is not a guarantee. Our BSC token checker guide explains what each flag means, and the BEP-20 token explorer lists verified contracts for USDT, USDC, BTCB and other majors so you never paste a fake one.
Blocks and the live BNB Smart Chain dashboard
A block result shows the block number, its hash and parent hash, the validator that produced it, the timestamp, the number of transactions, gas used against the block gas limit (70 million since September 2026) and the block size in bytes. Previous and next buttons let you walk the chain block by block, and the list of transactions inside is clickable. When you open the page without a query, the tool shows a live dashboard instead: current block height, average block time, gas price, BNB price and the most recent blocks with their transaction counts. It is a quick way to check that the network is healthy before you blame your wallet.
How to share a result or copy a proof of payment
Screenshots of explorer pages are the oldest trick in the scam book. They are trivial to edit, and they prove nothing about which chain, which token or which recipient. A link is different: the person receiving it opens the page, and the data is read fresh from the blockchain on their device. That is why every result in this tool comes with a share bar.
Share opens your phone’s native share sheet, so you can drop the link into any messenger. Copy link copies a permanent URL of the form /explorer/?q=0x…, with &net=opbnb or &net=bsc-testnet added for other networks. Dedicated buttons send it straight to Telegram, WhatsApp or X.
For transactions there is one more button: Copy payment receipt. It copies a short plain-text summary that reads well in any chat, email or support ticket:
✅ Payment on BNB Smart Chain: Confirmed
Amount: 250 USDT
From: 0x (sender address)
To: 0x (recipient address)
Timestamp: 24 Sep 2026, 14:02:11
Confirmations: 1,284
Tx: 0x (transaction hash)
Check it yourself: https://bnb-explorer.com/explorer/?q=0x…Notice that the “To” line in the receipt is the token recipient, not the token contract, so the other side sees who got paid. Freelancers paste it into invoices, P2P traders into order chats, and shops into refund tickets. How many confirmations are enough? With BNB Smart Chain’s fast finality a block is final in a little over a second, so for everyday payments one or two confirmations already mean the transfer cannot be reversed. Many merchants still wait for 15 or so — at 0.45 seconds per block that is under seven seconds.
Getting paid in USDT or BNB?
Convert to your local currency or top up gas on a licensed exchange operating since 2013.
Which networks: BSC mainnet, testnet and opBNB
The switch above the results covers the three EVM networks of BNB Chain. BSC Mainnet (chain ID 56) is where real payments, DeFi and BEP-20 tokens live — this is the default. BSC Testnet, also called Chapel (chain ID 97), uses valueless tBNB for developers; the full workflow with faucets is in our BNB testnet explorer guide. opBNB (chain ID 204) is BNB Chain’s OP Stack layer 2, popular with games and high-frequency apps; see the opBNB and Greenfield explorer overview. The same address can exist on all three with different balances, and a transaction hash exists on only one. If a lookup comes back empty, switching networks is the first thing to try. Want your wallet to open the right explorer by itself? Our MetaMask network setup guide shows the correct block explorer URLs.
Where the data comes from — and what it cannot do
Everything is fetched live, in your browser, from free public sources. Blocks, transactions, receipts, balances and contract calls come from BNB Chain’s own public JSON-RPC endpoints, with automatic failover to PublicNode, 1RPC and dRPC when one is slow. Token symbols and decimals are read with eth_call straight from each contract. Token holdings and address history come from the Binplorer API, security flags from GoPlus Security, and the BNB price from CoinGecko.
That design has honest limits. The official public nodes disable eth_getLogs and do not index addresses, so a node alone cannot answer “list every transfer this wallet ever made”. We lean on Binplorer for that, which is why holdings and history appear only on mainnet and show the most recent 25 entries. Public endpoints are rate-limited (BNB Chain allows 10,000 requests per five minutes per IP), so on a very busy day a lookup may need a retry. Very old history can occasionally fail on a backup endpoint. And we do not show internal transactions (BNB moved by contracts), full traces or verified source code — those need an archive-and-trace index, which is what full explorers are for. If you are building something on top of this kind of data, our BNB Chain explorer API guide lists every free endpoint and its limits.
Privacy: nothing stored, no login
There is no account, no wallet connection and no API key. Your browser talks directly to the public nodes and APIs listed above; our server only delivers the page. We do not keep a log of what you searched. The one place a query lives is the URL — that is what makes results shareable — so if you do not want someone to see which wallet you checked, do not send them the link. And a reminder that applies to every explorer: no legitimate lookup will ever ask for your seed phrase or ask you to “connect wallet to verify a transaction”. If one does, close the tab.
When to open BscScan or BSCTrace instead
Use this tool for fast checks, sharing and receipts. Switch to a full explorer — the result page links to both — when you need something only a complete index has: verified contract source and Read/Write tabs, internal transactions and traces, address labels such as “Binance Hot Wallet”, token holder lists, complete history with CSV export, watchlists and alerts, or contract verification. BscScan is the deepest for labels and contract tools — see our BscScan review. BSCTrace from NodeReal is cleaner and comes with a free developer API — covered in the BSCTrace review. And when either is down or slow, the BscScan alternatives page has backups that read the same chain.