Solana Inspector.

1. Prepare your transaction JSON

   Use a saved Solana getTransaction response from your own provider, with jsonParsed encoding. Retain the transaction, signatures, slot, account references, instructions and execution metadata, including the supplied balances and logs.

   Accepted shapes: a JSON-RPC response envelope, its transaction result object, or an array of those objects. The input must retain the original execution record, not only a decoded summary.

   A screenshot, a wallet address or signature alone, or a provider’s summarized swap object is not the same input. The inspector does not download transactions. Keep original address casing. Do not put API keys, provider URLs, seed phrases or private keys in the file.

2. Download, verify, then install

   Download the package, checksum file and synthetic example JSON from the release panel. Put them in a new, empty working folder and open your terminal there. Do not rename the files. The commands below verify the package and example before installing; a mismatch means stop and download again from this site.

   The local package is named @z7onlabs/solana-inspector and its command is z7on-inspect. It has no registry dependencies or install scripts. Installation uses your downloaded archive, not a package fetched from npm. The 0.4.0 inspector source is separate from the private application repository.

   PowerShell / Windows

   1. Verify both files and install offline

   $ErrorActionPreference = 'Stop'
   $expectedPackage = '25af612df021347a7b14522c0f325f0f3f37fb83ceaf19f3d07433e1295f26c6'
   $expectedExample = 'c006074402127c2988cb17d984bc5e00860d89d5e5d5641327868183bc9b7c14'
   if ((Get-FileHash -LiteralPath './z7onlabs-solana-inspector-0.4.0.tgz' -Algorithm SHA256).Hash.ToLowerInvariant() -ne $expectedPackage) { throw 'Package checksum mismatch. Do not install.' }
   if ((Get-FileHash -LiteralPath './example.json' -Algorithm SHA256).Hash.ToLowerInvariant() -ne $expectedExample) { throw 'Example checksum mismatch. Do not run.' }
   npm install './z7onlabs-solana-inspector-0.4.0.tgz' --ignore-scripts --offline --no-audit --no-fund
   if ($LASTEXITCODE -ne 0) { throw 'Installation failed.' }

   2. Inspect the synthetic example and reproduce it

   npx --no-install z7on-inspect --input ./example.json --wallet 11111111111111111111111111111112 --out ./example-report
   if ($LASTEXITCODE -ne 0) { throw 'Inspection failed.' }
   npx --no-install z7on-inspect --input ./example-report/manifest.json --wallet 11111111111111111111111111111112 --out ./example-replay
   if ($LASTEXITCODE -ne 0) { throw 'Replay failed.' }

   3. Open the report from your disk

   Start-Process -FilePath './example-report/report.html'

   The command opens your default browser. No local server is required.

   Shell / Linux

   1. Verify both files and install offline

   set -eu
   printf '%s  %s\n' '25af612df021347a7b14522c0f325f0f3f37fb83ceaf19f3d07433e1295f26c6' 'z7onlabs-solana-inspector-0.4.0.tgz' | sha256sum --check -
   printf '%s  %s\n' 'c006074402127c2988cb17d984bc5e00860d89d5e5d5641327868183bc9b7c14' 'example.json' | sha256sum --check -
   npm install './z7onlabs-solana-inspector-0.4.0.tgz' --ignore-scripts --offline --no-audit --no-fund

   2. Inspect the synthetic example and reproduce it

   npx --no-install z7on-inspect --input ./example.json --wallet 11111111111111111111111111111112 --out ./example-report
   npx --no-install z7on-inspect --input ./example-report/manifest.json --wallet 11111111111111111111111111111112 --out ./example-replay

   3. Open the report from your disk

   xdg-open ./example-report/report.html

   On desktop Linux this opens your default browser. On a headless machine, open report.html later in a browser; a desktop opener is not needed for inspection or replay. No local server is required.

   The example is synthetic, not from blockchain. It demonstrates a sponsored fee and a deliberate unexplained balance difference. Its explanation lists the expected exact amounts. A completed command with an unresolved observation is expected; do not turn its residual into a proven incoming payment.

3. Use your own file and wallet

   npx --no-install z7on-inspect --input "./your-transaction.json" --wallet "REPLACE_WITH_YOUR_WALLET_ADDRESS" --out "./your-report"

   After installation, replace the placeholders with your local JSON path, the subject wallet’s exact Solana address and a new output directory. Keep inputs and outputs separate. The parent directory must already exist; the output directory must not. The inspection runs offline: it does not query a provider or send the file to this website. The command uses the installed local binary, without fetching a missing package. Open your-report/report.html from disk. To reproduce it, use your-report/manifest.json as the input with the same wallet and another new output folder.

pnpm inspector:build

pnpm inspector -- --input <file> --wallet <address> --out <new-dir>

Exact movements

Token quantities, account effects and fees with their evidence. Preserve raw amounts and decimals rather than relying on a rounded display value.

Scoped reconciliation

Which observed amounts agree, which accounts are affected and where ownership, ordering or an unexplained difference blocks interpretation. Missing observations are not zero balances.

Reproducible evidence

Input fingerprints, methodology and source references alongside the conclusions. Keep the original files with the result so a later inspection can use the same evidence. A manifest from a different inspector version is rejected explicitly, not converted.

Explicit limitations

Unknown effects stay unresolved. The local inspector does not provide complete wallet PnL, tax advice, identity verification or a safety certification.

No email, files, wallet addresses, transaction signatures, secrets or local paths are requested. Do not include them in free-text answers. Package version and a local receipt code are optional. The inspector never opens this form or sends a receipt automatically.

The form is hosted by Google. Responses are private to the brand account and used to improve the tool and assess usefulness. Individual responses are retained until 90 days after the experiment closes; afterwards, only aggregated conclusions are kept. This does not promise anonymity from Google. There is no inspector telemetry or embedded survey in your offline report.