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 Transaction count Methodology

## 1. Overview

Transaction count measures the total number of confirmed transactions added to the Hydration network. This metric reflects the level of active user engagement and protocol throughput across the ecosystem, including activity within Hydration DEX and Hydration Lending. Data is captured from both the native Substrate layer and the Ethereum Virtual Machine (EVM) compatible layer to provide a comprehensive view of network utilization.

## 2. Data sources

- **Blockchain events**: Extrinsics from Hydration Substrate and `Executed` events from the `ethereum` pallet on Hydration EVM

## 3. Step-by-step calculation

### Component A: Hydration Substrate transaction extraction

- **Purpose**: Capture native transactions initiated on the Hydration Substrate chain.
- **Logic**: Extrinsics are extracted from the native Substrate chain. Each transaction is identified by a unique extrinsic identifier and associated with its corresponding block timestamp. This captures all native-level operations and pallet interactions.
- **Key fields**: `block_timestamp`, `extrinsic_id`

### Component B: Hydration EVM transaction extraction

- **Purpose**: Capture transactions executed through the Ethereum-compatible layer.
- **Logic**: `Executed` events are parsed from the `ethereum` pallet. To ensure unique identification within the Substrate event structure, a transaction identifier is constructed by concatenating the extrinsic ID with the event index. This ensures that every EVM execution is accounted for as a distinct transaction.
- **Key fields**: `block_timestamp`, `extrinsic_id`, `event_index`

### Component C: Daily aggregation and deduplication

- **Purpose**: Consolidate transaction data into daily time series.
- **Logic**: Transaction identifiers from both the Substrate and EVM layers are combined into a single dataset. The metric is calculated by counting distinct transaction identifiers per day. Timestamps are truncated to UTC midnight boundaries. In instances where no activity is detected, values are zero-filled to maintain a continuous historical record.
- **Key fields**: `block_timestamp`, `extrinsic_id`

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

Confirmed transactions added to the blockchain.

HydrationHDX

Transaction count

Transaction count

Competitive landscape

Chain breakdown