Finding Historical Transaction Throughput Benchmarks and Fee Tables Listed Directly on the Project's Webpage Document
Why Official Documentation Matters for TPS and Fee Data
When evaluating a blockchain or crypto platform, relying on third-party aggregators often introduces delays or rounding errors. Official project webpages typically host a dedicated “Performance” or “Metrics” section where raw historical transaction throughput (TPS) and fee schedules are published. These documents, often in JSON or CSV format, allow direct verification of peak loads, average confirmation times, and cost per operation. Unlike explorer sites that show real-time data, official archives preserve snapshots of past network states, enabling accurate backtesting.
Projects like Solana, Ethereum, and Polygon maintain changelogs that link to archived benchmark reports. For example, Solana’s documentation includes a “Historical TPS” tab that records daily averages since mainnet launch. Similarly, fee tables are often embedded in whitepapers or developer guides, detailing gas limits, base fees, and priority tiers. Accessing these primary sources eliminates the risk of misinterpretation from secondary analytics tools.
How to Locate and Interpret Benchmarks
Navigating the Project’s Webpage Structure
Start by checking the “Docs” or “Resources” section. Many projects list a “Network Statistics” page with a direct link to a historical CSV. For instance, Ethereum’s gas tracker page provides a downloadable log of daily average fees since 2015. Look for terms like “throughput_report.csv” or “fee_history.json”. These files are often updated quarterly and include columns for date, block height, TPS, and median fee.
Reading Fee Tables for Cost Analysis
Fee tables typically show base fees in gwei (Ethereum) or lamports (Solana). Historical tables reveal how fee structures changed after protocol upgrades (e.g., EIP-1559). Compare pre- and post-upgrade rows to see if costs stabilized or spiked. For throughput, note that TPS benchmarks may distinguish between “peak” and “sustained” values-the latter is more reliable for capacity planning.
Common Pitfalls When Using Official Data
One frequent error is ignoring timestamps: a benchmark from a testnet stress event may not reflect mainnet conditions. Always filter for “mainnet” tags. Another issue is fee table currencies-some projects list fees in USD equivalents, which fluctuate with token price. Convert to native token units for consistent historical comparison. Also, watch for missing data during network upgrades; official documents sometimes omit days when the chain halted.
Cross-reference multiple snapshots. If a project’s page only shows the last 30 days, use the Wayback Machine to retrieve older versions. For example, archived copies of the Algorand performance page reveal TPS data from 2020 that is no longer displayed on the live site.
FAQ:
How often do projects update their historical TPS tables?
Most update quarterly, but major networks like Bitcoin and Ethereum publish weekly logs. Check the page’s “Last Updated” timestamp.
Can I trust fee tables that show values in fiat currency?
No-fiat values change with market price. Always convert to native units (e.g., wei, satoshis) for accurate historical analysis.
What if the project’s webpage has no downloadable data?
Look for an API endpoint (e.g., /api/v1/historical_tps) or check the project’s GitHub repository for archived metrics files.
Do throughput benchmarks include failed transactions?
Usually not-official tables count only confirmed transactions. Failed ones are excluded unless specifically noted in the document.
Reviews
Marcus J.
I used Solana’s official TPS CSV to backtest a trading bot. The data was clean, with no gaps. Saved me hours of scraping.
Elena R.
The Ethereum fee table from 2021 showed a clear spike during the NFT boom. Cross-referencing with the archive confirmed my thesis.
Carlos D.
I nearly used a third-party site that rounded fees. The official Polygon document had exact values in MATIC. Crucial for my research.