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

Pendulum is a decentralized blockchain for cross-border payments and traditional finance infrastructure powered by Polkadot Relay chain.

PEN holders own and govern the protocol. Pendulum is a subsidiary of SatoshiPay. SatoshiPay's investors include Blue Star Capital, KR1 plc, Stellar Development Foundation, etc.

website

twitter

github

discord

Blockchains (L2)

Pendulum

# Pendulum Transaction count Methodology

## 1. Overview

The Pendulum transaction count metric measures the daily number of unique transactions (extrinsics) executed on the Pendulum parachain. This metric provides insight into the daily activity level and usage of the Pendulum blockchain network. The calculation counts distinct extrinsic identifiers on a daily basis, representing all types of transaction-like operations on the parachain.

## 2. Data sources

The metric uses the following raw data sources:

- **Pendulum blockchain extrinsics**: Raw transaction data from the Pendulum parachain containing all extrinsic operations with unique identifiers and block timestamps
- **Chain availability configuration**: Metadata indicating when the Pendulum chain was active and data collection was reliable

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extracts and prepares raw transaction data from the Pendulum blockchain
- **Logic**: Selects extrinsic records from Pendulum blockchain data, casting the `block_timestamp` field to timestamp format and `extrinsic_id` to string format. Each record represents a unique transaction or operation on the Pendulum parachain. The chain identifier is set to 'pendulum' for all records.
- **Key fields**: `block_timestamp` (when the transaction was processed), `extrinsic_id` (unique transaction identifier), `chain_id` (blockchain identifier)

### Component B: Daily aggregation
- **Purpose**: Groups transactions by day and counts unique transactions
- **Logic**: Truncates block timestamps to day boundaries using timestamp truncation, then groups all transactions by the resulting daily timestamp. For each day, counts the number of distinct `extrinsic_id` values to determine the total number of unique transactions. Adds metadata fields including timestamp grain set to 'day', market sector identifier set to 'blockchains_l2', business segment identifier set to 'blockchain', and product identifier set to null.
- **Key fields**: `timestamp` (daily boundary), `transaction_count` (distinct count of extrinsics), `timestamp_grain`, `chain_id`, `market_sector_id`, `business_segment_id`

### Final aggregation
- **Combining components**: The daily aggregated transaction counts are processed through the finalize metric macro which standardizes the output schema and validates data integrity
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation to day granularity
- **Final calculation**: The final metric value is the count of distinct extrinsic identifiers for each day, representing the total number of unique transactions processed on the Pendulum parachain. Gap filling strategy applies zeros for any missing days to ensure continuous time series data. Chain availability filtering excludes periods when the chain was not active or data collection was unreliable.

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

Confirmed transactions added to the blockchain.

PendulumPEN

Archived

Transaction count

Transaction count

Competitive landscape

Chain breakdown