website

twitter

Blockchains (L1)

Plasma

# Plasma Transaction count Methodology

## 1. Overview

The Plasma transaction count metric measures the daily number of unique transactions occurring on the Plasma blockchain. This metric provides insight into the daily transaction activity and network usage of the Plasma protocol. The calculation aggregates unique transaction hashes by day and recipient address, providing granular visibility into transaction volume patterns.

## 2. Data sources

The metric relies on two primary blockchain data sources:
- **Plasma transaction records**: Raw transaction data from the Plasma blockchain containing transaction hashes, sender and recipient addresses, gas usage metrics, effective gas prices, block timestamps, and block numbers
- **Plasma block records**: Block-level data from the Plasma blockchain containing block numbers and base fee per gas information used in the EIP-1559 fee model

## 3. Step-by-step calculation

### Component A: Transaction data preparation
- **Purpose**: Creates a comprehensive transaction dataset by combining transaction records with block-level fee information
- **Logic**: Raw Plasma transaction records are joined with corresponding block records using the `block_number` field. Transaction data is standardized with proper data type casting for timestamps, addresses, and numeric fields. Block data provides the `base_fee_per_gas` information that complements the transaction's `effective_gas_price`. Additional metadata is added including the hardcoded token address and symbol for Plasma's native token XPL
- **Key fields**: `block_timestamp` for timing, `transaction_hash` as unique identifier, `from_address` and `to_address` for transaction parties, `gas_used` and `effective_gas_price` for fee calculations, and `base_fee_per_gas` from block data

### Component B: Daily transaction aggregation
- **Purpose**: Aggregates transaction data into daily counts grouped by recipient address
- **Logic**: Transaction timestamps are truncated to day-level granularity using timestamp truncation. Transactions are then grouped by the truncated timestamp and recipient address (`to_address`). For each group, the count of distinct transaction hashes is calculated to determine the number of unique transactions. Standard metadata fields are assigned including chain identifier as 'plasma', market sector as 'blockchains_l1', and business segment as 'blockchain'
- **Key fields**: `timestamp` (truncated to day), `chain_id`, `market_sector_id`, `business_segment_id`, `to_address`, and `transaction_count` (distinct count of transaction hashes)

### Final aggregation
- **Combining components**: The daily aggregated transaction data flows through a finalization macro that validates the data structure, ensures proper schema compliance, and handles any data gaps using a zero-fill strategy for missing days
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation to day level, with incremental processing handling recent data updates
- **Final calculation**: The final metric value represents the count of distinct transaction hashes occurring on each day for each recipient address on the Plasma blockchain, providing granular daily transaction volume measurements

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

Confirmed transactions added to the blockchain.

PlasmaXPL

Transaction count

Transaction count

Competitive landscape