MERX / Methodology v1

Every number needs context.

Our public statistics describe observed tariffs and confirmed blockchain activity. The following rules define what each series includes.

← Back to statistics

Comparable energy packages

We record published rental tariffs for 65,000 and 131,000 energy, covering at least one hour, for an already activated address. When the shortest available tariff has a longer billed term, that term is shown. We do not prorate a longer rental into an advertised one-hour price.

The comparison covers the sources displayed on the statistics page. It is a monitored subset of the market. Activation, funding, withdrawal and transaction fees are excluded. These package sizes are not a guarantee of how much energy a particular USDT transfer will need.

Sources, freshness and coverage

We reuse MERX’s existing provider polls. Actual successful observations are generally around 60–90 seconds apart. For the daily series we select the latest preceding observation on a five-minute UTC grid, accepting source data no more than 120 seconds old.

Daily prices use paired observations with PowerSun and at least two external sources. A complete report requires a closed UTC day and at least 95% of its 288 observation points. Missing values are not zero and are never interpolated. Partial days remain labelled and do not enter the historical chart.

TEM and TronSave snapshots do not provide the exact standard-package total needed for this version of the comparison. They remain visible as excluded sources. Netts’s reported limit describes where its tariff applies; it is not measured market liquidity. A successful poll or a published tariff is not a guarantee that an order can be filled.

MERX estimates

The displayed MERX estimate applies the current pricing rule to the monitored, eligible reference tariffs. It is a model, not a binding quote or an executed trade. A final quote can use additional exact provider quotes and address-specific charges.

Potential savings compare the model and reference tariff at the same observation time. They are not proven customer savings. We do not describe all burned TRX as avoidable waste, or infer network-wide rental savings from the lowest current tariff.

Confirmed network activity

The network collector processes solidified TRON blocks sequentially. It checks each block against its complete transaction receipts, validates chain continuity and saves the aggregate with its progress marker in one transaction. Restarting or replaying a block cannot add its figures twice.

USDT events are identified using the official contract TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t and the Transfer event signature. Only successful transfers contribute to USDT activity. Token movements include internal transfers and are not a measurement of retail payments, purchases or unique people.

Energy and Bandwidth burn come from transaction receipts. For transactions containing several USDT transfers, the whole transaction’s fees are counted once. Those fees may also cover other activity in the same transaction. Network-wide fee totals include fees paid by failed transactions. Rental payments are outside these on-chain burn totals.

A receipt does not reliably distinguish the sender’s own staked energy from rented energy. We therefore do not publish an own-versus-rented split. Delegation counts are not sales, revenue or provider market share.

History and publication

All new daily reports use UTC. The first network day is partial, because collection starts during the day. A network day becomes complete only after the collector continuously processes the confirmed chain into the next day. Older raw analytics and the legacy mixed-duration price archive are not used to claim complete historical coverage.

Reports publish automatically when at least one dataset meets its completeness criteria. Unavailable sections are labelled. The RSS feed links to these reports; we do not create near-identical articles for every incomplete interval.

Price history is available as CSV; market and network data are available as JSON. You may cite the public aggregates with a link to the relevant MERX daily report and this methodology.

Price data · JSONNetwork data · JSONTRON knowledge base