github

twitter

discord

website

Blockchains (L2)

Boba Network

# Boba Network Transaction count Methodology

## 1. Overview

The Boba Network transaction count metric measures the daily number of unique transactions executed on the Boba Network L2 blockchain. This metric answers the business question: "How many distinct transactions occur on Boba Network each day?" The calculation aggregates individual blockchain transactions by day and counts unique transaction hashes, providing insight into network activity and adoption levels.

## 2. Data sources

- **Boba Network transaction records**: Raw blockchain transaction data including transaction hashes, block timestamps, sender and recipient addresses, and gas usage information
- **Boba Network block data**: Block-level data with precise timestamps used for daily aggregation boundaries
- **L1 and L2 gas metrics**: Gas usage data specific to Layer 2 networks, including both L2 execution costs and L1 data availability costs

## 3. Step-by-step calculation

### Component A: Transaction data standardization
- **Purpose**: Prepares raw Boba Network transaction data for aggregation by standardizing field types and adding metadata
- **Logic**: Extracts transaction records from Boba Network blockchain data and casts all fields to appropriate data types. The `block_timestamp` field is cast to timestamp format, `transaction_hash` and address fields are cast to strings, and gas-related fields are cast to high-precision numeric types. Metadata is added including the chain identifier, token information (hardcoded ETH token with dead address), and L2-specific gas metrics like `l1_gas_used`, `l1_gas_price`, and `l1_fee_scalar`
- **Key fields**: `block_timestamp` (transaction timing), `transaction_hash` (unique identifier), `from_address` and `to_address` (transaction participants), gas usage metrics for both L1 and L2 components

### Component B: Daily transaction aggregation  
- **Purpose**: Groups transactions by day and counts unique transactions, segmented by destination address
- **Logic**: Block timestamps are truncated to daily boundaries using day-level granularity. Transactions are grouped by the truncated date, destination address (`to_address`), and various metadata fields including chain identifier, market sector, and business segment. Within each group, distinct transaction hashes are counted to ensure each unique transaction is counted exactly once, even if it appears multiple times in the raw data
- **Key fields**: `timestamp` (daily boundary), `to_address` (destination segmentation), `transaction_count` (distinct hash count)

### Final aggregation
- **Combining components**: The daily aggregated transaction counts are processed through the finalize metric transaction count macro which validates the data schema and ensures data quality standards
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day level, ensuring all transactions within a 24-hour period are grouped together
- **Final calculation**: The final metric represents the count of distinct transaction hashes per day per destination address on Boba Network. Gap-filling logic ensures that any missing dates in the time series are filled with zero values to maintain continuous daily data. Chain availability filtering is applied to ensure the data meets quality standards before being exposed as the final metric.

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

Confirmed transactions added to the blockchain.

Boba NetworkBOBA

Transaction count

Transaction count

Competitive landscape

Chain breakdown