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 Transaction count Methodology

## 1. Overview

The Phala transaction count metric measures the total number of unique transactions (extrinsics) processed on the Phala blockchain each day. This metric provides insights into network activity and adoption by counting distinct transaction executions. The calculation aggregates raw blockchain extrinsic records on a daily basis, ensuring each unique transaction is counted exactly once per day.

## 2. Data sources

The calculation relies on the following raw data sources:

- **Phala blockchain extrinsic records**: Raw transaction data from the Phala blockchain containing extrinsic identifiers, block timestamps, and transaction metadata. Each extrinsic represents a unique transaction or function call executed on the Phala network.
- **Chain availability configuration**: Metadata defining valid data coverage periods for the Phala blockchain to ensure metric accuracy during data availability windows.

## 3. Step-by-step calculation

### Component A: Transaction data preparation
- **Purpose**: Standardizes raw Phala extrinsic records for metric calculation
- **Logic**: Raw extrinsic records from the Phala blockchain are selected and standardized. Each record contains a block timestamp indicating when the transaction was processed, a unique `extrinsic_id` identifying the specific transaction, and the chain identifier set to 'phala'. The `block_timestamp` field is cast to timestamp format for consistent time-based processing.
- **Key fields**: `block_timestamp` for temporal grouping, `extrinsic_id` as the unique transaction identifier, and `chain_id` for blockchain classification

### Component B: Daily transaction aggregation  
- **Purpose**: Counts unique transactions per day on the Phala blockchain
- **Logic**: Transaction records are grouped by truncated timestamp to day-level granularity using timestamp truncation to the day boundary. For each day, the system counts distinct `extrinsic_id` values to ensure each unique transaction is counted exactly once. The aggregation includes metadata fields for timestamp grain ('day'), chain identifier, market sector ('blockchains_l2'), and business segment ('blockchain'). Incremental processing applies a lookback window to process recent data efficiently, filtering to dates greater than or equal to the last partition date minus lookback days.
- **Key fields**: Truncated daily `timestamp`, `transaction_count` as the distinct count of extrinsics, classification metadata for reporting structure

### Final aggregation
- **Combining components**: The daily aggregated transaction counts are processed through a finalization macro that standardizes the metric schema, validates identifiers, and ensures temporal continuity
- **Gap filling**: Missing days in the time series are filled with zero transaction counts using the 'fill_zeros' strategy to maintain complete daily coverage
- **Chain availability filtering**: Results are filtered to include only periods where Phala blockchain data is available and reliable, excluding dates outside the valid data coverage window
- **Final calculation**: The metric represents the count of distinct `extrinsic_id` values per day, providing the total number of unique transactions processed on the Phala blockchain for each calendar day

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

Confirmed transactions added to the blockchain.

PhalaPHA

Archived

Transaction count

Transaction count

Competitive landscape

Chain breakdown