twitter

discord

website

Blockchains (L1)

Movement

# Movement Transaction count Methodology

## 1. Overview

The Movement transaction count metric measures the daily number of unique transactions processed on the Movement blockchain. This metric provides insight into network activity and adoption by counting distinct transactions that occur each day. The calculation aggregates raw blockchain transaction data to produce daily counts of unique transaction hashes, with special handling for genesis transactions and incremental processing for efficient data updates.

## 2. Data sources

- **Movement blockchain transactions**: Raw transaction records from the Movement blockchain including transaction hashes, block timestamps, sender addresses, gas usage, and gas unit prices
- **Transaction metadata**: Details such as transaction hashes for uniqueness identification, block timestamps for temporal aggregation, and gas-related fields for comprehensive transaction records

## 3. Step-by-step calculation

### Component A: Transaction data extraction and processing
- **Purpose**: Extract and standardize all Movement blockchain transaction records for counting
- **Logic**: Retrieve all transaction records from Movement blockchain data, including transaction hashes, block timestamps, sender addresses, gas usage, and gas unit prices. Apply timestamp filtering to exclude transactions with timestamps before 2000-01-01, except for genesis transactions which are handled separately. Genesis transactions (those with timestamps before 2000-01-01) are assigned a hardcoded timestamp of 2024-12-05 00:00:00 UTC to properly position them in the timeline. Gas unit prices are converted from raw values to standardized decimal format by dividing by 10^8.
- **Key fields**: `transaction_hash` for uniqueness counting, `block_timestamp` for daily aggregation, `sender` for transaction origin, `gas_used` and `gas_unit_price` for transaction cost analysis

### Component B: Daily transaction aggregation
- **Purpose**: Group transactions by day and count unique transaction hashes
- **Logic**: Truncate block timestamps to day granularity to create daily boundaries. Group all transactions by the truncated timestamp and count distinct transaction hashes within each day. This ensures that each unique transaction is counted exactly once per day, regardless of any potential duplicate records. Add metadata fields including timestamp grain set to 'day', chain identifier set to 'movement', market sector as 'blockchains_l2', business segment as 'blockchain', and product identifier as null.
- **Key fields**: `timestamp` as the daily boundary, `transaction_count` as the distinct count of transaction hashes per day

### Final aggregation
- **Combining components**: The daily transaction counts flow directly from the aggregation component without requiring additional joining of separate data sources
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Daily boundaries are created using timestamp truncation to day level, ensuring consistent 24-hour periods for counting
- **Final calculation**: The final metric represents the count of distinct transaction hashes that occurred within each day on the Movement blockchain. The finalization macro validates the schema structure, ensures data completeness by filling any gaps with zero values, and applies chain availability filtering. Incremental processing includes a configurable lookback period to handle late-arriving or updated transaction data.

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

Confirmed transactions added to the blockchain.

MovementMOVE

Archived

Transaction count

Transaction count

Competitive landscape