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 Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of confirmed user transactions added to the Polkadex blockchain each second. It reflects both the network’s throughput and real-time usage. Daily transaction counts are converted into a standardized per-second rate that can be compared across different blockchain networks and time periods.

## 2. Data sources

- **Blockchain events**: Extrinsic records and transaction logs from the Polkadex substrate-based blockchain, covering Polkadex

## 3. Step-by-step calculation

### Component A: Raw transaction extraction

- **Purpose**: Extract and standardize raw transaction data from the Polkadex blockchain
- **Logic**: Raw extrinsic records for blocks produced prior to January 10, 2025, are selected from Polkadex blockchain records, with `block_timestamp` fields cast to timestamp format and `extrinsic_id` fields cast to string format for consistency. Each record is labeled with `chain_id` as 'polkadex' to identify the source blockchain.
- **Key fields**: `block_timestamp`, `extrinsic_id`, `chain_id`

### Component B: Daily transaction count aggregation
- **Purpose**: Aggregate individual transactions into daily totals while applying proper business categorization
- **Logic**: Transactions are grouped by day using timestamp truncation of `block_timestamp` to daily boundaries. Distinct `extrinsic_id` values are counted to avoid double-counting any transactions. Each daily record is classified with `market_sector_id` as 'blockchains_l2', `business_segment_id` as 'blockchain', and `chain_id` as 'polkadex'. The `product_id` field is set to null as this metric applies to the entire blockchain rather than specific products.
- **Key fields**: `timestamp`, `timestamp_grain`, `transaction_count`, `chain_id`, `market_sector_id`, `business_segment_id`

### Component C: Final aggregation and TPS calculation

- **Purpose**: Convert daily transaction counts into a standardized per-second rate
- **Logic**: Daily transaction counts are converted to transactions per second by dividing the `transaction_count` by the number of seconds in a day (86,400 seconds). Currency conversion is not applicable for this count-based metric. Data is aggregated at daily boundaries using timestamp truncation, then converted to per-second averages. The transactions per second value is calculated using safe division to handle potential null or zero values. Consistent time series data with no missing days is ensured through schema validation and gap-filling with zeros.

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

Average confirmed user transactions added per second.

PolkadexPDEX

Archived

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown