What the BNB Chain user is confirming
BNB Smart Chain validators use Proof of Staked Authority to propose blocks and cast Fast Finality votes, while EVM execution processes transactions and smart-contract calls against account-based state.
BNB Chain (BNB): How BNB Smart Chain Gas and Transactions Work
BNB Smart Chain is an EVM-compatible Layer 1 blockchain within the BNB Chain ecosystem, and BNB is its native asset. The network uses an account-based state model where externally owned accounts and contract accounts interact through transactions executed by the EVM. This page focuses on how BNB Smart Chain Gas and Transactions Work and the checks users need before sending funds, paying fees or using the network.
Help users understand how BNB Smart Chain gas works and make safer usage and transaction decisions for BNB Chain.
- Snapshot:
- CoinGecko - USD
- Chart:
- Binance Spot - BNB/USDT
- Timezone:
- UTC
Use this page to check reference market data and understand how BNB Smart Chain accounts, gas and transactions work. It is educational reference material, not an executable exchange quote or trading recommendation.
Content ownership: BitcoinToolkit Editorial Team
Technical references: Official BNB Chain documentation and source repositories.
Review approach: Technical explanations are checked against official BNB Smart Chain documentation and source repositories.
Last content review: Data integration last tested:
How BNB Smart Chain Gas and Transactions Work
BitcoinToolkit separates CoinGecko's aggregated USD reference from the Binance Spot BNB/USDT market, shows the source and age of each dataset, and provides sourced explanations of BNB units, gas, accounts, transactions and finality.
BNB and transaction costs
BNB Chain (BNB) is the asset profiled on this page.
BNB Chain (BNB) pays the applicable transaction cost.
BNB Candlestick Chart
BNB/USDT · Binance Spot · UTC
Long ranges automatically use a compatible candle interval so the chart stays within the supported candle limit.
Historical Binance Spot candles are available. JavaScript is required for current-candle updates.
Recent OHLC and volume data
| Time (UTC) | Open (USDT) | High (USDT) | Low (USDT) | Close (USDT) | Volume (BNB) |
|---|---|---|---|---|---|
| Aug 25, 2026 17:00:00 UTC | 698.70 USDT | 699.45 USDT | 696.66 USDT | 698.86 USDT | 2,666.86 BNB |
| Aug 25, 2026 16:00:00 UTC | 700.08 USDT | 700.64 USDT | 697.54 USDT | 698.69 USDT | 4,388.23 BNB |
| Aug 25, 2026 15:00:00 UTC | 698.31 USDT | 700.42 USDT | 696.24 USDT | 700.07 USDT | 6,329.62 BNB |
| Aug 25, 2026 14:00:00 UTC | 694.48 USDT | 699.61 USDT | 693.25 USDT | 698.30 USDT | 7,886.87 BNB |
| Aug 25, 2026 13:00:00 UTC | 697.56 USDT | 698.28 USDT | 690.50 USDT | 694.48 USDT | 10,707.73 BNB |
Market data: Binance Spot BNB/USDT
Charting library: TradingView Lightweight Charts
BNB Smart Chain, BNB and Tokens
BNB Smart Chain is the EVM-compatible network, BNB is its native asset, and BEP-20 token balances are maintained by smart-contract state.
Page subject
BNB Smart Chain
Market pair
BNB/USDT
Network family
EVM Layer 1
Network
BNB Smart Chain executes account-based transactions and EVM smart contracts within the broader BNB Chain ecosystem.
Role distinction
Native BNB is not a BEP-20 token. Native balances belong to protocol account state, while BEP-20 balances belong to token-contract storage.
BNB Smart Chain Accounts
BNB Smart Chain tracks account-based state containing balances, nonces, contract code and contract storage.
Account-based state
The network state maps addresses to account data and changes as valid transactions execute.
Externally owned accounts
Externally owned accounts are controlled by private keys and can originate signed transactions.
Contract accounts
Contract accounts are controlled by deployed EVM bytecode and execute when called.
Nonce
A sender nonce orders transactions from an externally owned account and prevents replay on the same chain.
Balance
An account balance records native BNB assigned to the account.
Code execution
Contract bytecode executes in the EVM when a call reaches the contract.
Contract storage
Contracts can maintain persistent storage that changes after successful execution.
BNB Units
One BNB equals 1,000,000,000,000,000,000 wei on BNB Smart Chain.
Unit assetBNB
Native unitBNB
Smallest unitwei
Fee quote unitgwei
RPC unitwei
Conversion factor1 BNB = 10^18 wei; 1 gwei = 10^9 wei
Decimal precision18 decimal places
BNB (BNB)10^18 wei | 18 decimals
Gwei (gwei)10^9 wei | 9 decimals
Wei (wei)1 wei | 0 decimals
Wallets display BNB, gas prices are commonly quoted in gwei, and raw EVM transaction and RPC values use wei.
BNB Smart Chain Gas and Fees
Transactions pay for EVM computation in gas, using BNB as the native fee asset.
Gas
Gas measures computational work.
Gas limit
The gas limit caps how much work a transaction may consume.
Gas used
Gas used records the metered work consumed by execution.
Gas price
Gas price states the amount of BNB-denominated value offered per unit of gas.
Execution cost
The execution fee is determined by gas used and the effective per-gas price; wallet estimates can differ from final usage.
BNB Smart Chain Transactions
A transaction is created, signed, validated, propagated, executed by the EVM, recorded in a receipt, included in a block and later finalized.
- Transaction creationThe sender constructs recipient, value, data, nonce, gas and chain fields.
- SigningThe sender signs with the key controlling the account.
- Nonce validationNodes verify the sender nonce and transaction rules.
- BroadcastThe signed transaction is submitted to a BNB Smart Chain node.
- Node propagationEligible pending transactions are relayed between nodes.
- ExecutionThe EVM applies the transaction against the current state and meters gas.
- Receipt generationExecution produces a receipt containing status, gas information and logs.
- Block inclusionA validator includes the transaction in a proposed block.
- Finality stateFast Finality votes can finalize an included block; if votes are insufficient, applications rely on probabilistic confirmation depth until finality is reported.
BNB Smart Chain Contracts
BNB Smart Chain runs EVM smart contracts deployed as contract accounts.
Contract accounts
Contract accounts contain code and can be called by transactions or other contracts.
Bytecode execution
Compiled bytecode executes in the EVM.
Storage
Contracts can read and update persistent storage.
Contract calls
Calls pass BNB value and encoded input data to contract code.
Token contracts
BEP-20 contracts maintain token balances, transfers and allowances.
Native asset and token roles
Native BNB belongs to protocol state; BEP-20 balances are managed by token contracts.
Proof of Staked Authority and Finality
BNB Smart Chain uses Proof of Staked Authority for block production and Fast Finality votes to finalize blocks when the required validator threshold is reached.
Consensus model
Proof of Staked Authority combines validator staking, elected validator participation and authority-based block production.
Validator model
Active validators take turns proposing blocks and use separate voting keys to participate in Fast Finality voting under protocol rules.
Block proposal
A scheduled validator proposes a block containing an execution payload.
Finality model
Fast Finality normally finalizes the chain within two blocks when at least two-thirds of validators vote normally. If finality votes are insufficient, the chain falls back to probabilistic finality, where additional confirmations increase confidence.
Application limitation
Applications requiring guaranteed finality should query the finalized block tag and must not treat block inclusion alone as finality.
Where BNB Chain Differs for Users
Before the next transaction
- Identify utility for the current BNB Chain route.
- Verify network for the current BNB Chain route.
- Check issuer rules for the current BNB Chain route.
- Use or transfer for the current BNB Chain route.
- Confirm custody for the current BNB Chain route.
Compare fees, execution, security and user workflow before choosing between BNB Chain and Avalanche.
BNB Chain Transaction and Fee Checks
What BNB Chain users should verify and why this design differs
The CoinGecko USD snapshot and Binance Spot BNB/USDT chart are separate datasets and can differ. Market reference data may be delayed or unavailable when a provider cannot return validated values.
For BNB Chain, the practical sequence is Identify utility, Verify network, Check issuer rules, Use or transfer, Confirm custody. Confirm the official destination and current network, then inspect the final balance, position, receipt or documented exit state that actually completes the task: Understand how BNB Smart Chain gas works and make safer usage and transaction decisions for BNB Chain.
Before treating the BNB Chain task as complete, confirm each of these states separately: Identify utility, Verify network, Check issuer rules, Use or transfer, Confirm custody. The final check should use the current official interface, explorer or documented accounting state rather than a copied ticker or an interface notification alone.
When an action fails, preserve the transaction hash or application reference, then compare it with the current official documentation before retrying. Repeating the same action without identifying the failed step can duplicate approvals, fees, deposits or position changes.
The fee asset and the profiled BNB asset should be treated as separate roles unless current documentation proves they are the same for this route. A user may hold the market asset and still lack the network balance, allowance or service payment required to finish the action.
Use dated primary sources for parameters that can change, including supported networks, contract addresses, validator rules, withdrawal timing, service availability and fee behavior. A previously valid workflow can become incomplete after a migration, upgrade or application-policy change.
BNB Chain Ecosystem use FAQ
Is BNB a BEP-20 token?
Native BNB is the protocol asset used for value transfer and gas. BEP-20 token balances are maintained by contracts.
What pays transaction fees on BNB Smart Chain?
Transaction execution fees are paid in native BNB and depend on gas used and the effective gas price.
Are the USD snapshot and BNB/USDT chart the same market?
No. CoinGecko supplies an aggregated USD reference, while the chart represents Binance Spot BNB/USDT.
Known Limitations
- Applications should use current finalized-block data and confirmation policies appropriate to their risk model.
Market Data Methodology
The snapshot uses CoinGecko aggregated USD data. The chart uses Binance Spot BNB/USDT data. Their providers, venue coverage and quote currencies differ, so displayed values can differ. Missing or malformed values remain unavailable; verified cached data must be labeled Cached or Delayed.
The snapshot is CoinGecko aggregated USD data. The chart is Binance Spot BNB/USDT data. Their providers, venue coverage and quote currencies differ, so displayed values can differ.
- Market Snapshot Source
- CoinGecko aggregated market data (USD)
- Candlestick Source
- Binance Spot market data
- Pair
- BNB/USDT
- Venue
- Binance Spot
- Market Type
- Spot
- Timezone
- UTC
- Cache
- Snapshot cache is approximately 60 seconds; historical candle cache varies by interval.
- Failure Handling
- Verified cache is labeled Cached or Delayed. Missing values remain unavailable.
- Snapshot Status
- Fresh
- Chart Status
- Historical Only
- Report Issue
- Report a market-data problem →
Technical Sources
Selected primary sources support the operational explanations. Market-provider attribution remains separate.
Editorial Information
Verified technical content, reviewed sources and update history.
- Published
- Last Review
- Data Verification
- Sources
- Official documentation