Compare with another capture
Paste the JSON copied from another browser (or drop the downloaded file). Timing fields are ignored by default because they change on every run.
The sQ signal vector — what this loader would submit
Every value the sensor hands to its WASM core as sQ(<uint32 id>, value).
One row per id, in the order a genuine authenticated Chrome capture submitted them, produced by the
module linked on the right. Hover a value to see what that same id carried in the reference capture.
The cards further down are the full transcriptions these values come from — useful for understanding
a check, too verbose for diffing two browsers.
Module detail — full transcriptions (28 modules)
What am I looking at?
1b9be6.js is an obfuscated WASM-loader sensor. Its JavaScript glue reads browser state and
submits each value to the WASM as sQ(<uint32 id>, value). Each card below is one extracted
module that reproduces the original reads in the original order with the original guards, and shows the
value the sensor would submit. The sQ badges are the submission ids.
- Browser modules depend on the engine, OS, device and settings. These are the ones worth diffing.
- Page modules read this page (its scripts, stylesheets, element tree, resource timing), so they describe this site rather than the browser.
- Runtime modules measure timing, tamper state and tooling; their values drift between runs.
- Values are shown before the sensor's transport codecs (
yK/TO/Bo/m_) and without its random nonces, so they stay readable and comparable. - Gated means the original sensor would skip that collector on this engine (for example the WebKit-only private-mode probe).
Special values that JSON cannot carry are written as «undefined», «NaN»,
«function name», and so on. Each card's source link opens the exact module that produced it.