Network observations, controlled tests and calculation models, with data and code to download.
Browse network observations, controlled tests, calculation models and documentation reviews. Each report includes its method, data and scope.
4 reports match these filters.
One 0.2 LTC entry supplied 9.74% of fees; removing it lowered the base-chain sample mean from 4643.08 to 4190.70 litoshis.
Method & code · Data / results
144 fixed mainnet blocks, subsidy/fees/coinbase reconciliation and MWEB decomposition. Header-time window; no payer identity, live quote, DOGE income or mining-profit audit.
Version: Core 0.21.5.8 · frozen network snapshot 2026-10-04-v1
A 1 LTC revenue target across 500,000 charged vbytes requires a 200 litoshis/vB weighted average.
Method & code · Data / results
Nine declared fee-revenue targets and charged-vbyte scenarios. Not measured occupancy, maximum block size, future demand or an attack budget.
Version: Python Decimal · declared scenarios 2026-10-02-v1
Adding 0.51 times unchanged honest hashpower gives 33.77% of the enlarged total, not a majority.
Method & code · Data / results
42 additional-capacity scenarios with frozen manufacturer inputs. No inventory, rental-market census or attack-success probability.
Version: Python Decimal · declared scenarios 2026-10-02.1
Method & code · Data / results
Frozen prices and difficulty; manufacturer specifications, not wall-power measurements. Cooling and extra merged coins excluded from the published base model.
Version: Python Decimal calculations · release 2026-10-01.1
These are overlapping snapshots. Averaging the displayed fee values does not produce a transaction-weighted fee for the whole period. A provider's mempool is one view of the network.
Differences between timestamps in adjacent recorded block headers. Miner-set timestamps are not stopwatch measurements of confirmation time.
| Measure · last 30 days of available blocks | Observed result |
|---|---|
| Valid adjacent intervals | 17,245 |
| Median interval | 105.0 seconds |
| 90th percentile | 349.0 seconds |
| Intervals longer than 10 minutes | 291 |
| Missing heights inside the recorded range | 0 |
| Negative timestamp differences excluded | 0 |
| Observed block-hash replacements | 1 |
Each collection requests the latest 100 blocks. The initial window may include blocks mined before collection began; their first retrieval time is retained. Missing heights are excluded from adjacent-interval calculations. The most recent 100 heights are rechecked for changed hashes; deep reorganizations outside that window may be missed.
How much does consolidating many inputs change the size of a standard native SegWit payment? The model below assumes P2WPKH inputs, two P2WPKH outputs and an illustrative fee rate of 1 litoshi/vB. This is a size calculation, not a live fee quote.
| Inputs | Estimated vbytes | Model fee · LTC |
|---|---|---|
| 1 | 141 | 0.00000141 |
| 10 | 753 | 0.00000753 |
| 100 | 6,873 | 0.00006873 |
Our separate mainnet observer study records a fixed sample of newly observed mempool transactions, their matched block inclusions, open waits and collection gaps. Its page shows node synchronization and collection status. Block timestamps in this archive remain a different measurement.
MWEB private transfer amounts, individual users and merchant sales are not inferred from these snapshots. Missing values remain missing.
