Build once, connect everywhere. Hyperbridge gives developers the secure infrastructure to scale applications across any network.

website

twitter

github

discord

Bridges

Hyperbridge

# Hyperbridge Transaction count Methodology

## 1. Overview

The Hyperbridge transaction count metric measures the daily number of unique transactions (extrinsics) processed on the Hyperbridge blockchain. This metric answers the business question: "How many distinct transactions occur on Hyperbridge each day?" The calculation aggregates unique transaction identifiers by day, providing a fundamental measure of blockchain network activity and usage.

## 2. Data sources

The metric relies on the following raw data sources:

- **Hyperbridge blockchain data**: Raw extrinsics records from the Hyperbridge blockchain, containing transaction-like operations with block timestamps and unique identifiers
- **Incremental processing metadata**: Token Terminal's internal table modification cache used for optimizing incremental data updates (does not contribute to metric values)

## 3. Step-by-step calculation

### Component A: Transaction extraction
- **Purpose**: Extract and standardize transaction records from raw Hyperbridge blockchain data
- **Logic**: Retrieves all extrinsics from the Hyperbridge blockchain, casting the `block_timestamp` field to timestamp format and the `extrinsic_id` field to string format. Adds a constant `chain_id` field set to "hyperbridge" for identification purposes. For incremental processing, filters to only include records from recent days based on the last partition date plus a configurable lookback period
- **Key fields**: `block_timestamp` (when the transaction was included in a block), `extrinsic_id` (unique identifier for each transaction), `chain_id` (set to "hyperbridge")

### Component B: Daily aggregation
- **Purpose**: Aggregate transaction counts on a daily basis
- **Logic**: Groups transaction records by day using timestamp truncation to daily boundaries. Counts distinct `extrinsic_id` values within each day to determine the number of unique transactions. Sets standardized fields including `timestamp_grain` to "day", `chain_id` to "hyperbridge", and `product_id` to "Hyperbridge Substrate"
- **Key fields**: `timestamp` (truncated to day boundary), `transaction_count` (count of distinct extrinsic IDs), `timestamp_grain`, `chain_id`, `product_id`

### Final aggregation
- **Combining components**: The daily aggregated data flows through a standardization macro that validates the data structure, ensures consistent schema formatting, and fills any missing dates with zero transaction counts using a "fill_zeros" strategy
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with each day representing a complete 24-hour period
- **Final calculation**: The final metric value is the count of distinct `extrinsic_id` values for each day, processed through standardization macros and filtered for chain availability to ensure data quality and completeness

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

Confirmed transactions added to the blockchain.

HyperbridgeBRIDGE

Archived

Transaction count

Transaction count

Competitive landscape

Chain breakdown