What this tool does
Analyzes Ethereum keystore JSON structure to show KDF settings (scrypt/pbkdf2), cipher, and parameters.
This page focuses on practical, step‑by‑step usage for **Ethereum Keystore File Analyzer**, with clear examples and common pitfalls.
When you should use it
Use it for recovery planning, migrations, and checking whether the keystore uses strong KDF settings.
How to use
- Paste the keystore JSON.
- Review KDF type and parameters (N, r, p / iterations).
- Confirm cipher mode and salt/IV lengths.
Quick example
Example: Verify a keystore uses scrypt with sufficiently high N before relying on it for long-term storage.
Notes
Do not paste keystores containing real funds unless you’re in a secure, offline environment.
Ethereum Keystore File Analyzer
Professional analysis for Ethereum keystore files (UTC--JSON) with address extraction and security assessment
What We Extract From Your Keystore File:
Extract 0x... Ethereum addresses from keystore
Analyze encryption and key derivation parameters
Identify AES, scrypt, and PBKDF2 parameters
Evaluate encryption strength and vulnerabilities
Prepare for John the Ripper & Hashcat cracking
Version, creation time, and client information
Upload Ethereum Keystore File
Drop your Ethereum keystore file here or click to browse
Supports UTC-- JSON keystore files (max 10MB)
Analyze Keystore JSON
Already have keystore JSON? Paste it below for instant analysis
Security First - Your Privacy Matters
We do NOT store or save your keystore files. All processing happens locally in your browser.
Your keystore file is processed entirely in your browser. No data is sent to our servers.
We do not collect, log, or monitor any personal information. Your analysis remains private.
All processing happens in memory. Files are never written to disk on our servers.
Important Security Notice
Never upload keystore files containing significant funds to any online service.
Even with local processing, browser-based tools have inherent security risks.
For high-value wallets, use air-gapped computers and offline tools.
Ethereum Keystore Quick Reference
Example Keystore Structure
{
"version": 3,
"id": "uuid-string",
"address": "0x...",
"crypto": {
"ciphertext": "encrypted-data",
"cipherparams": {"iv": "initialization-vector"},
"cipher": "aes-128-ctr",
"kdf": "scrypt",
"kdfparams": {
"dklen": 32,
"salt": "salt-value",
"n": 262144,
"r": 8,
"p": 1
},
"mac": "message-authentication-code"
}
}
FAQ
Is Ethereum Keystore File Analyzer encryption?
No. It is primarily an analysis/encoding utility. If you need confidentiality, use a real encryption scheme and manage keys properly.
What should I do if the input fails to decode/parse?
Start by checking for missing padding, wrong alphabet/variant, or extra whitespace. If the data looks multi-layered, try decoding step-by-step (e.g., URL decode → Base64 decode).
Can I use this with real wallet secrets?
Only if you’re in a secure/offline environment. Seed phrases, keystores, and private keys can control funds; treat them as extremely sensitive.