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

Polkadex is a fully non-custodial peer-to-peer orderbook-based cryptocurrency exchange for the DeFi ecosystem powered by Polkadot Relay chain.

PDEX holders own and govern the protocol. Polkadex’s investors include OKX Ventures, Outlier Ventures, Kenetic, etc.

website

github

twitter

discord

etherscan

Blockchains (L2)

Polkadex

# Polkadex Transaction count Methodology

## 1. Overview

Transaction count measures the daily number of unique transactions executed on the Polkadex blockchain. This metric serves as a key indicator of network activity and user engagement. Unique extrinsic records are aggregated by day, where each extrinsic represents a transaction or function call submitted to the Polkadex network.

## 2. Data sources

- **Blockchain events**: Extrinsic records from the Polkadex blockchain for the period ending January 10, 2025
- **External data**: Chain availability configuration defining operational periods and data collection status for Polkadex

## 3. Step-by-step calculation

### Component A: Transaction data extraction

- **Purpose**: Extract and standardize raw transaction records from the Polkadex blockchain
- **Logic**: Extrinsic records are retrieved from Polkadex blockchain data for the period ending January 10, 2025. The `block_timestamp` field is cast to a standard timestamp format and the `extrinsic_id` is cast to a string for consistent processing. Each record represents a unique transaction or function call submitted to the network. The timing of when each transaction was included in a block and its unique identifier within the Polkadot ecosystem are included in the data.
- **Key fields**: `block_timestamp` (when the transaction was processed), `extrinsic_id` (unique transaction identifier), `chain_id` (set to 'polkadex')

### Component B: Daily aggregation

- **Purpose**: Group transactions by day and count unique transactions per day
- **Logic**: Transaction timestamps are truncated to daily boundaries using day-level granularity, grouping all transactions that occurred within the same calendar day. Distinct `extrinsic_id` values are counted within each day to ensure that duplicate or repeated transaction records do not inflate the count. Standard metadata fields are added including market sector classification as 'blockchains_l2' and business segment as 'blockchain'.
- **Key fields**: `timestamp` (daily boundary), `transaction_count` (distinct count of extrinsics), classification metadata

### Component C: Final aggregation and filtering

- **Purpose**: Finalize daily transaction counts and apply filters
- **Logic**: Daily transaction counts are processed through a finalization macro that validates the data schema, ensures consistent field formatting, and implements gap-filling logic. Currency conversion is not applicable for transaction count metrics. Data is aggregated at daily boundaries with each day representing a complete 24-hour period in UTC. The final metric value represents the count of unique extrinsics processed each day on Polkadex for the supported historical period. Zero values are filled for operational days when no transactions occurred, and data is filtered to exclude periods when the chain was not operational or data collection was inactive.

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

Confirmed transactions added to the blockchain.

PolkadexPDEX

Archived

Transaction count

Transaction count

Competitive landscape

Chain breakdown