Collators aggregate parachain transactions block candidates and producing state transition proofs for validators based on those blocks.

Phala is a specialized privacy-preserving cloud computing blockchain powered by Polkadot Relay chain.

PHA holders own and govern the protocol. Phala’s investors include IOSG Ventures, Incuba Alpha, Candaq Fintech Group, and others.

website

twitter

discord

github

etherscan

Blockchains (L2)

Phala

# Phala Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed per second on the Phala blockchain over daily periods. This metric provides insight into the network's transaction throughput and usage patterns. The calculation divides the total daily transaction count by the number of seconds in a day (86,400) to derive an average TPS value.

## 2. Data sources

- **Phala blockchain extrinsics**: Raw transaction data from the Phala parachain containing all executed transactions (called extrinsics in Substrate-based blockchains)
- **Transaction metadata**: Block timestamps and unique transaction identifiers from the Phala substrate chain

## 3. Step-by-step calculation

### Component A: Transaction facts extraction
- **Purpose**: Extract and standardize raw Phala transaction data for further processing
- **Logic**: Raw Phala extrinsics data is processed to extract relevant transaction information. Each record represents a unique transaction (extrinsic) executed on the Phala blockchain. The `block_timestamp` field is cast to a proper timestamp format, and each transaction is assigned a unique `extrinsic_id`. The chain identifier is set to 'phala' to distinguish this data from other blockchain networks.
- **Key fields**: `block_timestamp` (when the transaction was processed), `extrinsic_id` (unique transaction identifier), `chain_id` (set to 'phala')

### Component B: Daily transaction count aggregation
- **Purpose**: Aggregate raw transaction data into daily transaction counts
- **Logic**: Transaction data is grouped by day by truncating the `block_timestamp` to daily granularity. For each day, the system counts distinct `extrinsic_id` values to determine the total number of unique transactions processed. The aggregation includes metadata fields for market sector classification ('blockchains_l2') and business segment ('blockchain'). Missing days are filled with zero values to ensure complete time series data.
- **Key fields**: `timestamp` (daily date), `timestamp_grain` (set to 'day'), `transaction_count` (count of distinct transactions), `chain_id`, `market_sector_id`, `business_segment_id`

### Final aggregation
- **Combining components**: Daily transaction counts are processed to calculate the final TPS metric by dividing the total transaction count by the number of seconds in a day
- **Currency conversion**: Not applicable for this transaction volume metric
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation to day level
- **Final calculation**: The transactions per second value is calculated by dividing the daily `transaction_count` by 86,400 (the number of seconds in a day). This provides an average TPS value representing the typical transaction throughput across each 24-hour period. The result shows how many transactions per second the Phala network processed on average for each day.

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

Average confirmed user transactions added per second.

PhalaPHA

Archived

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown