Data Methodology

    Every data page on this site states its source and its age. This page explains the system behind those labels.

    Last reviewed: May 2026

    Current data sources

    DataProviderRefresh
    Bitcoin fee rates, mempool, block height, difficultymempool.spaceCached up to 60 seconds
    Crypto Fear & Greed IndexAlternative.mePublished daily, cached up to 1 hour
    Coin prices, market cap, volume, supply, 24h high/low, all-time high/lowCoinGeckoCached up to 15 minutes
    Price history charts (7D / 30D / 90D / 1Y, daily points)CoinGeckoCached up to 24 hours

    Providers are named on the page where their data appears, with a link to the source, so any figure can be checked independently.

    How the data is fetched

    Requests are made from our server, not from your browser, and the result is cached and shared across visitors. One upstream request therefore serves many page views. We normalise every provider response into our own internal format, so a provider can be replaced without changing what you see or how it is labelled.

    Market prices for the 25 assets on our market data pages are requested in a single batched call, not one call per coin, and no API key ever reaches your browser. Chart history is fetched at daily granularity and held only in a short-lived cache — we do not keep a permanent store of provider price history, and we do not redistribute it as a dataset.

    Market data: provider, caching and outages

    CoinGecko is our current market-data provider for coin prices, market caps, volumes, supply figures and price history. One batched server request covers all 25 assets and the result is targeted to refresh about every 15 minutes, so every visitor and every coin page reads the same shared snapshot. Chart history is refreshed at most once per asset per day and held in an operational cache; we keep no permanent copy of provider history.

    If a refresh fails, we keep showing the last good snapshot and label it as delayed, with its real age. If no recent reading exists at all, we say the data is temporarily unavailable rather than showing a stale or invented number. During a provider outage the rest of the page — editorial content, calculators and tools — continues to work.

    The timestamp on each module is the moment we last received the figure from the provider, not the moment you loaded the page. Prices differ between exchanges and between data providers because each aggregates a different set of markets, so our figures will not always match your exchange. They are for orientation and research only: we do not guarantee they are accurate enough to trade on, and nothing here is financial advice. Market data is provided by CoinGecko and attributed on every page where it appears.

    Freshness labels

    • Updated [time] ago — the reading is within its normal refresh window.
    • Delayed — the last refresh attempt failed and we are showing the most recent good reading, with its actual age.
    • Temporarily unavailable — no recent reading exists. We show a notice instead of a number.

    We never describe cached figures as "live" or "real-time", and we never substitute an estimate for missing data.

    Rounding and precision

    Fee rates are shown as the provider supplies them. Derived figures — mempool backlog in blocks, difficulty change, transaction cost illustrations — are rounded, and the rounding is deliberately coarse where extra decimal places would imply precision the underlying estimate does not have.

    Calculators

    Our calculators use no external data at all. They work from the values you enter, each page states the formula applied, and nothing you type is transmitted to us or stored. That is also why they continue to work when a data provider is down.

    Limitations

    • Fee estimates are probabilistic; confirm the rate in your own wallet.
    • Sentiment indices summarise attention and volatility, not value.
    • Third-party data can be wrong; we display it, we do not audit the provider.
    • Nothing on our data pages is financial advice or a prediction.

    Found a discrepancy? Our corrections policy explains how to report it, and our fact-checking policy covers claims outside these data feeds.