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

Polimec is a decentralized community-driven funding protocol powered by Polkadot Relay chain.

PLMC holders own and govern the protocol.

website

github

twitter

discord

Blockchains (L2)

Polimec

# Polimec Transaction count Methodology

## 1. Overview

The Polimec transaction count metric measures the daily number of unique transactions (extrinsics) processed on the Polimec blockchain. This metric provides insight into network activity and user engagement by counting all distinct transactions that occurred each day. The calculation uses raw blockchain extrinsic data and aggregates it to daily boundaries, ensuring no duplicate transactions are counted.

## 2. Data sources

The metric relies on the following raw data sources:
- **Polimec blockchain extrinsic records**: Raw transaction data from the Polimec blockchain containing unique transaction identifiers and execution timestamps
- **Polimec block timestamp data**: Timestamp information indicating when each transaction was included in a block on the Polimec network

## 3. Step-by-step calculation

### Component A: Transaction data preparation
- **Purpose**: Extract and standardize raw Polimec transaction data for aggregation
- **Logic**: The calculation begins by accessing raw Polimec extrinsic records, which represent individual transactions on the blockchain. Each extrinsic contains a unique identifier (`extrinsic_id`) and the timestamp when it was included in a block (`block_timestamp`). The data undergoes type casting to ensure proper data types, with timestamps converted to standard timestamp format and extrinsic IDs converted to string format. A constant chain identifier of 'polimec' is added to classify all transactions as belonging to the Polimec blockchain.
- **Key fields**: `block_timestamp` (when the transaction was processed), `extrinsic_id` (unique transaction identifier), `chain_id` (blockchain identifier set to 'polimec')

### Component B: Daily transaction aggregation
- **Purpose**: Group transactions by day and count unique transactions per day
- **Logic**: The transaction data is aggregated to daily boundaries by truncating block timestamps to the day level, ensuring all transactions within a 24-hour period are grouped together. For each day, the calculation counts distinct extrinsic IDs to determine the total number of unique transactions, preventing any duplicate counting. The aggregation includes standard metadata fields: timestamp grain set to 'day', chain identifier as 'polimec', market sector as 'blockchains_l2' (indicating Polimec is classified as a Layer 2 blockchain), business segment as 'blockchain', and product ID set to null (not applicable for blockchain-level metrics).
- **Key fields**: `timestamp` (daily timestamp boundary), `transaction_count` (count of distinct extrinsic IDs per day), metadata fields for classification

### Final aggregation
- **Combining components**: The daily aggregated data is processed through a finalization macro that validates the data schema and ensures consistent time series coverage
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation to day level
- **Final calculation**: The final metric value represents the count of distinct transactions (`extrinsic_id`) for each day, with gap filling applied to ensure zero values for days with no transactions, and chain availability filtering to maintain data quality standards

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

Confirmed transactions added to the blockchain.

PolimecPLMC

Archived

Transaction count

Transaction count

Competitive landscape

Chain breakdown