github

twitter

discord

website

Blockchains (L2)

Boba Network

# Boba Network Transactions per second Methodology

## 1. Overview

The transactions per second (TPS) metric measures the average number of transactions processed per second on the Boba Network blockchain on a daily basis. This metric provides insight into network activity and throughput by calculating the daily transaction volume divided by the total seconds in a day (86,400). The calculation aggregates all transactions within daily boundaries and converts the daily count to a per-second average rate.

## 2. Data sources

- **Boba Network transaction records**: Raw blockchain transaction data containing block timestamps, transaction hashes, sender and recipient addresses, gas usage metrics, and transaction metadata
- **Chain availability configuration**: System configuration data that determines which chains and time periods should be included in calculations
- **Incremental processing metadata**: Table modification timestamps used to optimize data processing and identify changed partitions

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extract and standardize raw Boba Network transaction data for processing
- **Logic**: Raw transaction records are selected from Boba Network blockchain data and cast to appropriate data types. Key fields include `block_timestamp` for timing, `transaction_hash` for unique identification, `from_address` and `to_address` for transaction participants, and gas-related fields for network usage metrics. A standard token address representing ETH is assigned since Boba Network is an Ethereum Layer 2 network.
- **Key fields**: `block_timestamp` for transaction timing, `transaction_hash` for unique identification, `from_address` and `to_address` for transaction flow, `gas_used` and related gas metrics

### Component B: Daily transaction aggregation  
- **Purpose**: Count unique transactions per day and prepare data for TPS calculation
- **Logic**: Transaction timestamps are truncated to daily boundaries using timestamp truncation to the day level. Transactions are grouped by this daily timestamp along with chain identifiers and metadata fields. The system counts distinct transaction hashes within each day to avoid double-counting any transactions that might appear multiple times in the raw data. Incremental processing logic filters data to only process recent partitions based on the maximum partition date plus a configurable lookback period.
- **Key fields**: Daily `timestamp` boundaries, `chain_id` set to 'bobanetwork', `transaction_count` as distinct count of `transaction_hash` values

### Component C: TPS calculation
- **Purpose**: Convert daily transaction counts to transactions per second averages
- **Logic**: The daily transaction count for each day is divided by the total number of seconds in a day (86,400) using safe division to handle any potential zero or null values. This produces an average transactions per second rate for each day. The calculation uses a configurable variable for seconds in day to maintain consistency across the system.
- **Key fields**: `transactions_per_second` calculated as daily `transaction_count` divided by 86,400 seconds

### Final aggregation
- **Combining components**: The TPS values are passed through a standardized finalization macro that ensures proper schema structure, validates identifiers, and handles data quality requirements
- **Currency conversion**: Not applicable - this metric measures transaction volume rather than monetary values
- **Time aggregation**: Data is aggregated to daily boundaries with timestamps truncated to day granularity. The metric represents the average TPS for each calendar day
- **Final calculation**: Daily transaction count divided by 86,400 seconds equals average transactions per second for that day. Missing days are filled with zero values to maintain continuity, and chain availability filters are applied to ensure only valid time periods are included in the final results.

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

Average confirmed user transactions added per second.

Boba NetworkBOBA

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown