Site profile
litecoin.watch
Built with gtag, web-vitals 6.2.2, @vitest/utils 5.0.2, stackedboost-shopify-assets 0.2.0. 5 pages and 18 stored files, last crawled 2026-10-06.
rank 11,597,176 4 libraries 1 identifier 6 third-party hosts 1 crawl open the site
Technologies and libraries
Recognised by fingerprinting the stored files and bundles against known releases; a version is the release the bytes match.
| Library | Version | Seen |
|---|---|---|
| gtag | 2026-10-06 | |
| web-vitals | 6.2.2 | 2026-10-06 |
| @vitest/utils | 5.0.2 | 2026-10-06 |
| stackedboost-shopify-assets | 0.2.0 | 2026-10-06 |
Tracking, tag and verification IDs
Public identifiers read out of the source. Each links to every other site in the index that carries the same one.
| What | Value | Found in |
|---|---|---|
| Google Analytics 4 measurement id (Google) | G-TXS2WK4XKQ | view source |
Third-party hosts
Hosts outside litecoin.watch that its pages load scripts, frames or stylesheets from, and that its own scripts name in absolute URLs (connect). Each links to every site loading from the same host.
| Host | Loaded as | Found in |
|---|---|---|
| api.blockchair.com | connect | view source |
| api.coingecko.com | connect | view source |
| cdn.jsdelivr.net | stylesheet | view source |
| fonts.googleapis.com | stylesheet | view source |
| litecoinspace.org | connect | view source |
| www.googletagmanager.com | script | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
One entry per crawl, newest first, with what changed since the crawl before: libraries, identifiers, third-party hosts and files. Historical versions stay viewable because the stored chunks are shared between versions, never copied.
-
first crawl
5 pages, 18 files, 316.3 KB; 4 libraries, 1 identifier, 6 third-party hosts
4 libraries added
- gtag
- @vitest/utils 5.0.2
- stackedboost-shopify-assets 0.2.0
- web-vitals 6.2.2
1 identifier added
- G-TXS2WK4XKQ Google Analytics 4 measurement id
6 third-party hosts added
18 files added
- https://litecoin.watch/ html
- https://litecoin.watch/search/ html
- https://litecoin.watch/articles/how-to-store-lit…-safely-a-complete-wallet-guide html
- https://litecoin.watch/articles/ html
- https://litecoin.watch/about/ html
- https://litecoin.watch/assets/js/calculator-core.js?v=6a06a0e5bdbd6b539c5e js
- https://litecoin.watch/assets/js/market-data.js?v=ee2c2616cfe8750c8efd js
- https://litecoin.watch/assets/js/navigation.js?v=776e87598e5896aa2433 js
- https://litecoin.watch/assets/js/tool-memory.js?v=fef11edd6ebfb5541924 js
- https://litecoin.watch/assets/js/content-events.js?v=2b222f606a859ebe1442 js
- https://litecoin.watch/assets/js/rum.js?v=650da0ab3228eaecccb0 js
- https://litecoin.watch/assets/js/ticker-top.js?v=c12c15fa367110a495ed js
- and 6 more
Questions about litecoin.watch
- How does PageSourceSearch know what litecoin.watch is built with?
- From the site's own source code. The crawler stores the exact bytes of its pages and first-party scripts; the libraries are recognised by fingerprinting that code against known releases, the identifiers are read out of the tag snippets, and the third-party hosts are the script, iframe and stylesheet sources in the HTML and the absolute URLs inside the scripts. Nothing is inferred from headers or guessed.
- How far back does the history of litecoin.watch go?
- To the first crawl the timeline lists. Every crawl records what the site looked like; when a file's content changes, its earlier version stays viewable because the stored chunks are never deleted, only mapped. A crawl that finds a file unchanged adds no copy.
- Can I see an older version of a script from litecoin.watch?
- Yes. In the stored files list, every date under a file opens the version that was live at that crawl, with the same viewer as the current one. The raw bytes can be downloaded from there.
- Which other websites use the same tracking IDs as litecoin.watch?
- Each identifier links to its reverse lookup, the list of every site in the index whose source carries the same id: the sites one analytics property or tag manager container is shared across.
Look up another site, browse sites by tracking ID, third-party host or technology. Site owners: see the crawler page for how stored pages are removed.