website

twitter

Blockchains (L1)

Plasma

# Plasma Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed by the Plasma blockchain network per second on a daily basis. This metric provides insight into the network's throughput and activity level by taking the total daily transaction count and dividing it by the number of seconds in a day (86,400). The calculation uses actual transaction data from the Plasma blockchain to provide an accurate measure of network utilization.

## 2. Data sources

- **Plasma transaction records**: Raw blockchain transaction data including transaction hashes, block timestamps, sender and receiver addresses, gas usage, and effective gas prices
- **Plasma block records**: Blockchain block data containing block numbers and base fee information used in the EIP-1559 fee model
- **Static network metadata**: Plasma network identifiers including the native token address (`0x6100e367285b01f48d07953803a2d8dca5d19873`), token symbol (`XPL`), and chain identifier

## 3. Step-by-step calculation

### Component A: Transaction data preparation
- **Purpose**: Extract and standardize raw Plasma blockchain transaction data
- **Logic**: Raw transaction records are extracted and cast to appropriate data types. Key fields include `block_timestamp` (converted to timestamp), `transaction_hash` (as string), `from_address` and `to_address` (as strings), `receipt_gas_used` (as bignumeric), and `receipt_effective_gas_price` (as bignumeric). The data is filtered and validated to ensure data quality.
- **Key fields**: `block_timestamp`, `transaction_hash`, `from_address`, `to_address`, `gas_used`, `effective_gas_price`

### Component B: Block data integration
- **Purpose**: Enrich transaction data with block-level information for complete EIP-1559 fee calculations
- **Logic**: Plasma block data is extracted containing `block_number` and `base_fee_per_gas` information. This block data is joined with transaction data using the `block_number` as the join key. The base fee information is essential for understanding the EIP-1559 fee model where total fees consist of base fees (burned) plus priority fees (paid to validators).
- **Key fields**: `block_number`, `base_fee_per_gas`

### Component C: Network identification
- **Purpose**: Add static Plasma network identifiers to the transaction data
- **Logic**: Each transaction record is enriched with static network metadata including the Plasma token address, token symbol, and chain identifier. This ensures all transactions are properly attributed to the Plasma network for cross-chain analytics.
- **Key fields**: `token_address`, `token_symbol`, `chain`

### Component D: Daily transaction aggregation
- **Purpose**: Count unique transactions per day to establish daily transaction volume
- **Logic**: Transaction data is grouped by day using `timestamp_trunc` on the `block_timestamp` field. For each day, distinct transaction hashes are counted to determine the total number of unique transactions. Additional metadata is added including timestamp grain (day), chain identifier (plasma), market sector (blockchains_l1), and business segment (blockchain). The aggregation excludes any duplicate transactions by using `count(distinct transaction_hash)`.
- **Key fields**: `timestamp`, `timestamp_grain`, `chain_id`, `transaction_count`

### Final aggregation
- **Combining components**: The daily transaction counts serve as the foundation for the TPS calculation. The finalization macro validates the data schema, ensures proper identification fields, and fills any gaps in the time series with zero values where no transactions occurred.
- **Currency conversion**: No currency conversion is required as this metric measures transaction frequency rather than monetary values.
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation. The time series is validated to ensure no missing days, with gaps filled using zero values to maintain continuity.
- **Final calculation**: Transactions per second is calculated by dividing the daily transaction count by the number of seconds in a day (86,400) using the `safe_divide` function. This provides the average transactions per second for each day, giving insight into network throughput and activity levels. Chain availability filters are applied to ensure data quality and exclude periods when the chain may not have been fully operational.

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

Average confirmed user transactions added per second.

PlasmaXPL

Transactions per second

Transactions per second

Competitive landscape