Validators process transactions and receive fees from users (supply-side fees).

BNB Chain is a smart contract platform for decentralized applications (a blockchain). BNB Chain was founded by Changpeng Zhao and launched in 2020.

BNB holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue).

github

twitter

discord

etherscan

website

Blockchains (L1)

BNB Chain

# BNB Chain Transactions per second Methodology

## 1. Overview

The BSC transactions per second (TPS) metric measures the average number of transactions processed per second across the BNB Smart Chain ecosystem, including both the main BSC Layer 1 chain and the opBNB Layer 2 chain. This metric provides insight into network activity and throughput by calculating the daily average transaction rate, expressed as transactions per second.

The calculation aggregates all unique transactions from both chains on a daily basis, then divides by the number of seconds in a day (86,400) to derive the average TPS for each day.

## 2. Data sources

The metric relies on the following raw data sources:

- **BSC blockchain transaction records**: Complete transaction data from the BNB Smart Chain including block timestamps, transaction hashes, sender and receiver addresses, and gas usage information
- **opBNB blockchain transaction records**: Transaction data from the opBNB Layer 2 chain including timestamps, hashes, addresses, and Layer 2-specific gas metrics
- **Account labels dataset**: Public labeling dataset that provides human-readable names and classifications for blockchain addresses, specifically filtering for BSC chain labels to identify known contracts and entities

## 3. Step-by-step calculation

### Component A: BSC transaction extraction
- **Purpose**: Extract and standardize transaction data from the main BSC Layer 1 chain
- **Logic**: Raw transaction records are filtered and processed to extract key transaction identifiers and metadata. Each transaction includes the `block_timestamp`, `transaction_hash`, sender and receiver addresses (`from_address`, `to_address`), gas usage information, and gas pricing data. The transactions are classified with market sector metadata as Layer 1 blockchain transactions and associated with the BSC product identifier.
- **Key fields**: `block_timestamp` for temporal grouping, `transaction_hash` for unique transaction identification, `to_address` for destination address analysis, and gas-related fields for potential fee calculations

### Component B: opBNB transaction extraction  
- **Purpose**: Extract and standardize transaction data from the opBNB Layer 2 chain
- **Logic**: Similar to BSC transactions, opBNB transaction records are processed to extract transaction identifiers and Layer 2-specific metadata. These transactions include additional Layer 2 fields such as `l1_gas_used`, `l1_gas_price`, and `l1_fee_scalar` that relate to Layer 2 fee structures. The transactions are classified as Layer 2 blockchain transactions and associated with the opBNB product identifier.
- **Key fields**: `block_timestamp`, `transaction_hash`, `to_address`, and Layer 2-specific gas fields for comprehensive transaction tracking

### Component C: Daily transaction aggregation
- **Purpose**: Aggregate transaction counts by day, chain, and destination address
- **Logic**: Transactions from both BSC and opBNB are grouped by truncated daily timestamps and destination addresses. For each combination of day, chain, and destination address, distinct transaction hashes are counted to ensure no double-counting of transactions. This creates daily transaction counts segmented by where transactions are directed, enabling analysis of contract activity versus general transfers.
- **Key fields**: `timestamp` (truncated to day), `chain_id` (BSC or opBNB), `to_address` for segmentation, and `transaction_count` as the aggregated metric

### Component D: Address labeling enrichment
- **Purpose**: Enrich transaction data with human-readable labels for destination addresses
- **Logic**: The daily transaction aggregations are joined with the account labels dataset to identify known contracts, exchanges, and other labeled entities. Addresses without labels are classified as "Unlabeled". This enrichment enables categorization of transaction activity by destination type while maintaining the core transaction counts.
- **Key fields**: `contract_name` derived from account labels, with all other transaction count and metadata fields preserved

### Final aggregation
- **Combining components**: The labeled transaction data undergoes a finalization process that validates data quality, ensures consistent schema structure, and fills any gaps in the time series with zero values to maintain complete daily coverage
- **Time aggregation**: Daily boundaries are maintained throughout the calculation, with all transactions grouped by day-level timestamps
- **Final calculation**: The final transactions per second metric is calculated by summing all daily transaction counts (across all chains, addresses, and categories) and dividing by 86,400 seconds (the number of seconds in a day) to produce an average TPS value for each day

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Average confirmed user transactions added per second.

BNB ChainBNB

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown