website

twitter

discord

github

Blockchains (L1)

Berachain

# Berachain Transactions per second Methodology

## 1. Overview

The Berachain transactions per second metric measures the average number of transactions processed per second on the Berachain blockchain, calculated on a daily basis. This metric provides insight into network throughput and activity levels by taking the total daily transaction count and dividing by the number of seconds in a day (86,400). The calculation aggregates all transaction types and converts the daily volume to a per-second average, offering a standardized measure of blockchain network utilization.

## 2. Data sources

The calculation relies on these underlying data sources:
- **Berachain block data**: Block records containing block timestamps, block numbers, and base fee per gas information from the Berachain blockchain
- **Berachain transaction data**: Individual transaction records including transaction hashes, from/to addresses, gas usage, gas prices, and block associations from the Berachain blockchain  
- **Chain availability configuration**: Metadata defining which chains and time periods should be included in the final output
- **Incremental processing metadata**: Table modification tracking data used to optimize incremental data refreshes

## 3. Step-by-step calculation

### Component A: Block data processing
- **Purpose**: Prepares Berachain block information with proper data types and timing
- **Logic**: Raw Berachain block data is processed by casting block timestamps to timestamp format, block numbers to integers, and base fee per gas values to big numeric format. This creates a clean foundation of block-level information needed for transaction processing.
- **Key fields**: `block_timestamp` provides timing information, `block_number` enables joining with transaction data, and `base_fee_per_gas` captures network fee dynamics

### Component B: Transaction data enrichment  
- **Purpose**: Combines transaction details with block timing information and adds Berachain-specific metadata
- **Logic**: Raw transaction records are joined with the processed block data using `block_number` as the join key. Transaction fields are cast to appropriate data types including transaction hashes, from/to addresses, gas usage, and gas pricing information. Each transaction record is enriched with hardcoded Berachain-specific values including the native token address and 'BERA' symbol designation.
- **Key fields**: `transaction_hash` uniquely identifies each transaction, `block_timestamp` provides precise timing, `from_address` and `to_address` identify transaction parties, and gas-related fields capture transaction costs

### Component C: Daily transaction aggregation
- **Purpose**: Counts unique transactions per day and adds categorical metadata
- **Logic**: Transaction data is grouped by daily time boundaries using timestamp truncation to the day level. For each day, the system counts distinct transaction hashes to determine the total transaction volume. Records are enriched with categorical metadata including 'berachain' as the chain identifier, 'blockchains_l1' as the market sector, and 'blockchain' as the business segment. The `to_address` field is preserved for additional granularity.
- **Key fields**: `timestamp` represents the daily boundary, `transaction_count` contains the distinct count of transactions, and metadata fields provide classification context

### Final aggregation
- **Combining components**: The daily transaction counts flow directly from the aggregation component to the final transactions per second calculation
- **Currency conversion**: No currency conversion is required as this metric measures transaction volume rather than monetary values
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with each day representing a complete 24-hour period
- **Final calculation**: The transactions per second value is calculated by taking the daily transaction count and dividing by the number of seconds in a day (86,400). This provides an average transactions per second rate for each day. The calculation uses safe division to handle any potential division errors, and the result represents the mean transaction throughput over the daily period. Additional processing includes schema validation, gap filling with zero values for missing days, and application of chain availability filters to ensure only valid time periods are included in the final output.

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

Average confirmed user transactions added per second.

BerachainBERA

Transactions per second

Transactions per second

Competitive landscape