website

twitter

Blockchains (L2)

Humanity Protocol

# Humanity Protocol Transaction count Methodology

## 1. Overview

The Humanity transaction count metric measures the daily number of unique transactions on the Humanity blockchain network, segmented by recipient address. This metric provides insights into network activity and usage patterns by tracking the volume of transactions flowing to different addresses each day. The calculation counts distinct transaction hashes grouped by recipient address and aggregated to daily granularity.

## 2. Data sources

The metric relies on:
- **Blockchain transaction data**: Raw transaction records from the Humanity blockchain network containing transaction hashes, sender addresses, recipient addresses, and block timestamps
- **Node data**: Transaction data extracted directly from Humanity blockchain nodes

## 3. Step-by-step calculation

### Component A: Raw transaction extraction
- **Purpose**: Extract and standardize raw transaction data from the Humanity blockchain
- **Logic**: Raw transaction records are sourced from the Humanity blockchain network. Each transaction record includes the transaction hash for unique identification, sender address (`from_address`), recipient address (`to_address`), and the block timestamp indicating when the transaction was included in a block. Data types are cast to ensure consistency with timestamp fields converted to timestamp format and address fields converted to string format.
- **Key fields**: `transaction_hash` (unique transaction identifier), `from_address` (transaction sender), `to_address` (transaction recipient), `block_timestamp` (transaction timing)

### Component B: Daily aggregation
- **Purpose**: Aggregate transaction data to daily granularity grouped by recipient address
- **Logic**: Transactions are grouped by day using timestamp truncation that converts the block timestamp to day-level granularity. The data is further grouped by recipient address (`to_address`) to track transaction volumes received by each address. Distinct transaction hashes are counted to ensure each unique transaction is counted only once, avoiding any potential duplication. The aggregation includes metadata labels identifying the chain as 'humanity', market sector as 'blockchains_l2', and business segment as 'blockchain'.
- **Key fields**: `timestamp` (daily timestamp), `to_address` (recipient address), `transaction_count` (count of distinct transactions)

### Final aggregation
- **Combining components**: The daily transaction counts by recipient address flow through a finalization macro that validates the data schema and ensures consistent formatting
- **Currency conversion**: No currency conversion is required as this metric counts transactions rather than monetary values
- **Time aggregation**: Daily boundary logic uses timestamp truncation to group transactions by calendar day. Missing days are filled with zero values to maintain consistent time series data
- **Final calculation**: The final metric value represents the count of distinct transaction hashes received by each address on each day, providing a complete view of daily transaction volumes across all recipient addresses on the Humanity blockchain network

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

Confirmed transactions added to the blockchain.

Humanity ProtocolH

Transaction count

Transaction count

Competitive landscape