Litecoin.watch · Research & practical tools
Data source status
Last successful observations, collection gaps and the scope of each source. This page reports our data pipeline, not the health of the Litecoin network.
Page generated 5 Oct 2026, 11:04 UTC. Reload to check again. Research sources are checked every 15 minutes; release metadata every six hours.
Storage protection
Capacity checks are current · Last check: 5 Oct 2026, 11:04 UTC. A private monitor runs every minute; the node also checks capacity every 15 seconds.
New collection pauses when its budget, write reserve or the 20 GiB minimum free-space threshold is reached. A missing or unreadable protection check also blocks new writes. Pauses do not mean zero activity on the Litecoin network.
| Dataset | Used | Budget | Write reserve | Status |
|---|---|---|---|---|
| Market rate caches | 0.03 MiB | 64.00 MiB | 4.00 MiB | New writes allowedNo storage restriction |
| Fee and price history | 0.01 MiB | 16.00 MiB | 2.00 MiB | New writes allowedNo storage restriction |
| Background price alerts | 5.03 MiB | 256.00 MiB | 16.00 MiB | New writes allowedNo storage restriction |
| Network archive and backups | 11.11 MiB | 2.00 GiB | 32.00 MiB | New writes allowedNo storage restriction |
| LTC/EUR liquidity captures | 23.32 MiB | 512.00 MiB | 64.00 MiB | New writes allowedNo storage restriction |
| Confirmation observations and daily exports | 34.80 MiB | 2.00 GiB | 128.00 MiB | New writes allowedNo storage restriction |
| Pruned Litecoin Core data | 5.64 GiB | 20.00 GiB | 1.00 GiB | New writes allowedNo storage restrictionNode service: active |
Warnings begin at 80% of a budget. Space is reserved before a new capture, database backup or export, so a job can pause before the displayed usage reaches 100%. Sizes include filesystem allocation; measurements during active writes can change between checks.
Liquidity captures retain 30 days; the working confirmation database retains 90 days; network backups retain 14 daily copies. Published daily ZIP archives and research observations are not deleted by this protection. They remain within the budget and can require an operator to move an archive or review capacity. A node stopped by this protection requires an operator restart after capacity is restored. Existing CPU and memory limits remain in place.
Scheduled collection: latest attempts and successful runs
| Task | Latest state | Last success |
|---|---|---|
| backup | ok | 5 Oct 2026, 02:17 UTC |
| confirmation observer | running | 5 Oct 2026, 11:03 UTC |
| fees | ok | 5 Oct 2026, 11:00 UTC |
| liquidity | ok | 5 Oct 2026, 11:00 UTC |
| market feed | running | 5 Oct 2026, 11:02 UTC |
| network | ok | 5 Oct 2026, 11:00 UTC |
| previous ltc | ok | 2 Oct 2026, 08:00 UTC |
| previous rates | ok | 4 Oct 2026, 08:00 UTC |
| push | ok | 5 Oct 2026, 11:04 UTC |
Archive checks
Collector, unique snapshots and block checks are recent. This does not certify every recorded value.
Backup and restore drill passed · Last successful restore: 5 Oct 2026, 02:17 UTC.
Daily online SQLite backup, independent restoration and integrity checks. The last 14 daily backups are retained on this server. This check does not establish an off-site backup or whole-site recovery.
Independent provider comparison
BlockCypher reported height 3,189,959. Comparison: same hash at the same height.
Retrieved 5 Oct 2026, 11:00 UTC. Secondary reported time: 5 Oct 2026, 10:58 UTC. Primary block last checked: 5 Oct 2026, 11:00 UTC.
The sources are requested at different moments. Different tip heights alone are not a disagreement. Only hashes at the same recorded height are compared; the primary metrics are never replaced by this check.
Comparison and anomaly thresholds →Values flagged for review · last 7 days
- 1 Oct 2026, 20:15 UTC — Mempool count increased more than tenfold and exceeded 1,000; retained for review.
Showing the latest 20 flags. Flagged observations remain in the dataset.
| Source | Collector state | Last attempt | Last success / source time |
|---|---|---|---|
| BlockCypher tip comparisonSeparate height/hash check; not a replacement for Blockchair metrics. | Recent valid observation | 5 Oct 2026, 11:00 UTC | 5 Oct 2026, 11:00 UTCSource: 5 Oct 2026, 10:58 UTC |
| Blockchair block window | Recent valid observation | 5 Oct 2026, 11:00 UTC | 5 Oct 2026, 11:00 UTCSource: 5 Oct 2026, 11:00 UTC |
| Blockchair dogecoin | Recent valid observation | 5 Oct 2026, 11:00 UTC | 5 Oct 2026, 11:00 UTCSource: 5 Oct 2026, 10:59 UTC |
| Blockchair litecoin | Recent valid observation | 5 Oct 2026, 11:00 UTC | 5 Oct 2026, 11:00 UTCSource: 5 Oct 2026, 10:59 UTC |
| GitHub Core releases | Recent valid observation | 5 Oct 2026, 10:00 UTC | 5 Oct 2026, 10:00 UTCSource: 5 Oct 2026, 10:00 UTC |
| Litecoin Space fee cacheExisting fee tracker cache. Freshness does not confirm that a new request would succeed. | Recent valid observation | Not recorded | 5 Oct 2026, 11:00 UTCSource: 5 Oct 2026, 11:00 UTC |
Collection coverage · last 7 UTC days
| UTC date | Collector attempts | Valid LTC snapshots | Valid block windows |
|---|---|---|---|
| 2026-09-29 | 96 | 96 | 95 |
| 2026-09-30 | 96 | 96 | 96 |
| 2026-10-01 | 96 | 96 | 94 |
| 2026-10-02 | 96 | 96 | 96 |
| 2026-10-03 | 96 | 96 | 96 |
| 2026-10-04 | 96 | 96 | 96 |
| 2026-10-05 · partial day | 45 | 45 | 45 |
There are 96 scheduled quarter-hour slots in a complete UTC day. The launch day is partial; successful repeated source timestamps are deduplicated in the research archive. A successful run count can therefore exceed the number of unique snapshots.
Private node observer
The confirmation-time study has its own Litecoin Core node and collection status. Initial synchronization and observer outages do not create eligible timing records. Its cohort and coverage table are separate from the quarter-hour provider archive above.
Other live tools
The home page, currency converter, market comparisons and alerts use separate feeds and display their own source times. This table is not a site-wide uptime claim. The transaction checker makes an on-demand lookup; a fresh network snapshot does not guarantee a transaction lookup will succeed.