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

Hydration is a Polkadot parachain specialized in trading, lending, and stablecoin issuance.

HDX holders own and govern the protocol. Hydration’s investors include KR1 plc, Hypersphere, etc.

website

twitter

github

telegram

discord

medium

governance

etherscan

Blockchains (L2)

Hydration

# Hydration Transactions per second Methodology

## 1. Overview

Transactions per second measures the average number of confirmed user transactions added to the Hydration network each second. It reflects both the network’s throughput and real-time usage across the protocol's native Substrate and Ethereum Virtual Machine (EVM) environments. This metric provides a standardized view of activity for Hydration Substrate and Hydration EVM.

## 2. Data sources

- **Blockchain events**: `Executed` events from the `ethereum` pallet and blockchain extrinsics, covering Hydration Substrate and Hydration EVM

## 3. Step-by-step calculation

### Component A: Hydration Substrate activity tracking

- **Purpose**: Identifies transactions occurring on the native Substrate layer of the network.
- **Logic**: Extrinsics are parsed from the Hydration Substrate chain. Each extrinsic is assigned a unique identifier to ensure accurate counting of individual operations.
- **Key fields**: `block_timestamp`, `extrinsic_id`

### Component B: Hydration EVM activity tracking

- **Purpose**: Identifies transactions occurring on the EVM-compatible layer of the network.
- **Logic**: `Executed` events are parsed from the `ethereum` pallet. Unique identifiers for these transactions are generated by concatenating the extrinsic identifier with the event index. This ensures that EVM executions are distinct from the underlying Substrate extrinsics that wrap them.
- **Key fields**: `block_timestamp`, `extrinsic_id`, `event_index`

### Component C: Daily transaction aggregation

- **Purpose**: Consolidates transaction data into daily totals for the entire protocol.
- **Logic**: Transactions from both Hydration Substrate and Hydration EVM are aggregated by day based on the block timestamp. A distinct count of transaction identifiers is performed to determine the total volume of confirmed transactions per 24-hour period.
- **Key fields**: `block_timestamp`, `extrinsic_id`

### Component D: Throughput normalization

- **Purpose**: Converts the daily transaction volume into a per-second average.
- **Logic**: The total daily transaction count is divided by the number of seconds in a standard day (86,400). This calculation produces the average number of transactions processed per second, providing a consistent measure of network throughput.
- **Key fields**: `transaction_count`, `seconds_in_day`

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

Average confirmed user transactions added per second.

HydrationHDX

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown