website

twitter

discord

github

Blockchains (L1)

Berachain

# Berachain Transaction count Methodology

## 1. Overview

The Berachain transaction count metric measures the daily number of unique transactions occurring on the Berachain blockchain. This metric provides insight into network activity and adoption by counting distinct transactions executed each day, broken down by recipient address. The calculation aggregates raw Berachain transaction data on a daily basis and applies standardized metric formatting to ensure consistent time series reporting.

## 2. Data sources

The calculation uses the following raw blockchain data sources:

- **Berachain transaction records**: Raw transaction data from the Berachain blockchain containing transaction hashes, sender/recipient addresses, gas usage, pricing information, and block timestamps
- **Berachain block records**: Block-level data including block numbers, timestamps, and base fee per gas information used to enrich transaction records

## 3. Step-by-step calculation

### Component A: Transaction data preparation
- **Purpose**: Extracts and standardizes raw Berachain transaction data with block-level enrichment
- **Logic**: Raw transaction records are extracted from Berachain blockchain data and cast to appropriate data types. Transaction records include `transaction_hash`, `from_address`, `to_address`, `block_timestamp`, gas usage (`receipt_gas_used`), gas pricing (`gas_price`, `max_priority_fee_per_gas`), and block identifiers. Block data is separately extracted including `block_number`, `block_timestamp`, and `base_fee_per_gas`. Transactions are enriched with block-level base fee information through an inner join on `block_number`. Each transaction record is augmented with hardcoded BERA token metadata (`token_address`: `0x6969696969696969696969696969696969696969`, `token_symbol`: `BERA`, `chain`: `berachain`)
- **Key fields**: `transaction_hash` (unique transaction identifier), `to_address` (recipient address), `block_timestamp` (transaction timing), `base_fee_per_gas` (enriched from block data)

### Component B: Daily transaction aggregation  
- **Purpose**: Aggregates unique transactions by day and recipient address
- **Logic**: Transaction timestamps are truncated to daily boundaries using day-level granularity. Transactions are grouped by the truncated daily timestamp and `to_address` (recipient). Within each group, distinct `transaction_hash` values are counted to determine unique transaction volume. Standard metric dimensions are added including `chain_id` set to `berachain`, `market_sector_id` set to `blockchains_l1`, `business_segment_id` set to `blockchain`, with `product_id` and `contract_name` set to null. The `timestamp_grain` is set to `day` to indicate daily aggregation
- **Key fields**: `timestamp` (daily boundary), `to_address` (transaction recipient), `transaction_count` (count of distinct transaction hashes)

### Final aggregation
- **Combining components**: The daily aggregated transaction data is processed through the `finalize_metric_transaction_count` macro which validates the schema structure and applies gap-filling logic
- **Currency conversion**: No currency conversion is required as this is a count-based metric
- **Time aggregation**: Data is aggregated to daily boundaries with any missing days filled with zero transaction counts using the `fill_zeros` strategy
- **Final calculation**: The final metric value represents the count of distinct transaction hashes per day per recipient address on Berachain. Chain availability filters are applied to ensure data quality and completeness. For incremental processing, the calculation includes a lookback window to capture any late-arriving or updated transaction data.

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

Confirmed transactions added to the blockchain.

BerachainBERA

Transaction count

Transaction count

Competitive landscape