Validators process transactions and receive validator rewards (supply-side fees).

MultiversX is a smart contract platform for decentralized applications (a blockchain). MultiversX was founded by Beniamin Mincu and launched in 2018.

EGLD tokenholders own and govern the protocol. They currently take a cut of the transaction fees paid and give the cut to smart contract deployers (revenue).

github

twitter

etherscan

website

Blockchains (L1)

MultiversX

# MultiversX Active addresses (daily) Methodology

## 1. Overview

Daily active addresses on Elrond measures the number of unique addresses that initiated at least one transaction on the Elrond blockchain on a given day. This metric provides insight into daily network activity and user engagement by tracking addresses that actively participate in transactions. The calculation uses externally scraped transaction data to identify unique daily transaction senders, which are then classified as active addresses.

## 2. Data sources

- **Elrond transaction data**: Daily counts of unique addresses that sent transactions on the Elrond blockchain, collected by an external scraping service that monitors network activity
- **External scraper data**: Pre-aggregated daily transaction sender counts from the Elrond network

## 3. Step-by-step calculation

### Component A: Raw transaction sender extraction
- **Purpose**: Extract and standardize daily transaction sender counts from external Elrond scraper
- **Logic**: Raw data from the Elrond scraper contains daily counts of unique addresses that initiated transactions. The data includes a timestamp and a value representing the count of transaction senders for that day. This raw data is processed to add blockchain metadata including chain identifier (`elrond`), market sector classification (`blockchains_l1`), business segment (`blockchain`), and user type classification (`Transaction sender`). The timestamp grain is set to `day` and the value is cast as a numeric type for downstream processing.
- **Key fields**: `timestamp` for the date, `value` containing the daily count of unique transaction senders, `chain` set to `elrond`, `user_type` set to `Transaction sender`

### Component B: User DAU aggregation and dimensional breakdown
- **Purpose**: Transform transaction sender counts into user DAU (daily active users) with multiple dimensional breakdowns
- **Logic**: The transaction sender data is processed into three dimensional views. First, a project-level view groups all activity under the `project_dbt_tag` dimension with no chain-specific breakdown. Second, a chain-level view maintains the `elrond` chain identifier for chain-specific analysis. Third, a user-type-level view preserves the `Transaction sender` classification for user type analysis. Each dimensional view contains the same underlying `user_dau` value (renamed from `transaction_senders`) but with different dimensional attributes for flexible analysis. The standardization macro fills missing days with zero values to ensure complete time series data.
- **Key fields**: `user_dau` containing the daily active user count, `dimensions` indicating the breakdown type (`project_dbt_tag`, `chain`, or `user_type`), `chain_id` for chain-specific records, `timestamp` and `timestamp_grain` for temporal organization

### Final aggregation
- **Combining components**: The final metric selects only the `chain` and `project_dbt_tag` dimensional breakdowns from the user DAU data, filtering out the user-type-specific breakdown
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Data is already aggregated at the daily level from the source scraper, with missing days filled with zeros to maintain complete time series
- **Final calculation**: The `user_dau` field is renamed to `active_addresses_daily` to align with standard blockchain terminology. The finalize metric macro applies consistent schema formatting and ensures proper data types. Chain availability filtering is applied to respect data availability windows for the Elrond blockchain. The final result represents the count of unique addresses that sent at least one transaction on each day, broken down by both overall project level and individual chain level.

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

Unique active addresses over a fixed 24-hour window.

MultiversXEGLD

Active addresses (daily)

Active addresses (daily)

Competitive landscape