CryptoFeeScope logo
CryptoFeeScope
Methodology

Methodology

CryptoFeeScope shows estimated fees and speeds for a typical transfer on each supported chain. Use these numbers for quick comparison, not as guaranteed quotes.

What you’re seeing

  • Estimated Tx Fee (USD/JPY): typical network fee for a basic transfer, shown in USD or JPY.
  • Estimated Confirmation Time (sec): rough time to first confirmation.
  • Status: Fast / Normal / Slow / Degraded as a congestion/latency indicator.

How it’s computed (high level)

  • EVM chains: RPC gas signals + fixed typical transfer gas limit + FX conversion (CoinGecko demo data).
  • Non-EVM chains: chain-specific RPC fee hints for a typical transfer (BTC fee-per-byte, SOL base/priority, XRP base fee, TRON resource costs).
  • If live fetches fail, cached values may be shown. Check cache age on Top/Stats (History/History updated labels).

Data quality (missing / insufficient)

  • 24h / 7d summaries show — (Insufficient data) when coverage is low or gaps are large.
  • Charts do not interpolate missing points; lines break or are not drawn.

Comparison notes

  • Chains differ in fee mechanics (gas, tx size, resources, L1 data), so values are directional, not strict apples-to-apples.
  • L2s and alternative fee designs can shift what “fee” represents versus L1s.
  • All figures are estimates for comparison, not guaranteed quotes.

Shared assumptions

  • Typical transfer: basic asset transfer without complex contract calls.
  • FX conversion: USD/JPY values are conversions, not quotes from a specific wallet.
  • Refresh cadence: snapshot JSON is refreshed roughly every 10 minutes in this demo build.
  • Not investment advice: numbers are indicative and may differ from what you pay.

Comparability (Apples-to-apples?)

  • CryptoFeeScope compares “typical transfer” estimates per chain. This is close to a common baseline for simple transfers, but it is not a guaranteed apples-to-apples quote across all chains.
  • Sending $100 instead of $10 usually does not change the network fee for most chains. Fees depend more on transaction type/size and congestion than transfer amount.
  • For stricter comparisons, we plan scenario modes in later versions (e.g., Native transfer / Stablecoin transfer / Swap).

Data sources (current demo)

  • Demo snapshot at /data/fee_snapshot_demo.json generated via GitHub Actions, hosted on Cloudflare Pages.
  • Price basis from CoinGecko Demo; fee hints are simplified for UX testing.
  • Planned: swap in production-grade APIs (mempool.space, gasprice.io, Blocknative, OKLink, DefiLlama, etc.) and surface provider labels per row.

Chain-level methodology

Click a ticker in the table (ⓘ) to jump to each section.

EVM chains: gasPrice via RPC, typical transfer gasLimit, price via CoinGecko (Gnosis Chain, Fantom, Cronos use the same model).

BTC

  • Assumption: typical on-chain transfer size (tx vbytes varies by inputs/outputs).
  • Limits: congestion and transaction size change the actual fee.

ETH

  • Assumption: native transfer (≈21,000 gas) with current base/priority estimate.
  • Limits: contract calls cost more.

BSC

  • Assumption: native transfer with typical gas usage; network pricing differs from ETH.
  • Limits: transaction type and congestion can shift final cost.

ARBITRUM

  • Assumption: L2 fee includes the L1 data component; shown as a typical estimate.
  • Limits: L1 data fees can fluctuate with congestion.

OPTIMISM

  • Assumption: L2 fee includes the L1 data component; shown as a typical estimate.
  • Limits: L1 data fees can fluctuate with congestion.

SOL

  • Assumption: base fee plus a typical priority fee (if used); most simple transfers are near base fee.
  • Limits: priority fees can rise under load.

TRON

  • Assumption: cost varies by Energy/Bandwidth; shown as a generic estimate.
  • Limits: resource availability changes the effective fee.

AVAX

  • Assumption: C-Chain EVM-style fee model with a typical transfer.
  • Limits: congestion and gas price swings affect the paid fee.

GNOSIS CHAIN

  • Assumption: EVM-style gasPrice from RPC with a typical transfer gas limit.
  • Limits: congestion and gas price swings affect the paid fee.

FANTOM

  • Assumption: EVM-style gasPrice from RPC with a typical transfer gas limit.
  • Limits: congestion and gas price swings affect the paid fee.

CRONOS

  • Assumption: EVM-style gasPrice from RPC with a typical transfer gas limit.
  • Limits: congestion and gas price swings affect the paid fee.

XRP

  • Assumption: network base fee estimate; can increase during load.
  • Limits: spikes in demand can raise the minimum fee.