EVMGlass connects source inspection, local execution, and review. Start with the question you want to answer.
Inspect a deployed contract
- Open Investigate, select Ethereum or BNB Chain, and paste an address.
- Check the block, source provider, runtime match and proxy implementation.
- Open source & permissions. Compiler analysis resolves imports and declarations. Checks and modifiers are evidence for access rules, not a complete authorization proof.
- Return using the investigation bar. Your notes and analysis remain in the same investigation.
Explain a transaction
- Paste a confirmed transaction hash into Investigate.
- Read the outcome, decoded function and arguments, attempted native value, execution fee, and receipt events.
- For failures, open execution replay and supply a debug-enabled RPC endpoint or import a Geth trace.
- Trace values may describe attempted calls. Committed storage and balance differences require state-diff evidence.
A token event without verified decimals is shown in base units. Event signatures alone do not prove token identity or net balances.
Test a call or a change
Simulate a call opens the original account at the investigation's pinned block hash, including proxy dependencies. Choose a caller, function, arguments and value; all changes remain local.
Test a change opens baseline and candidate source with shared dependencies and compiler settings. Supply constructor arguments and a custom call sequence, then edit the candidate. Each side deploys into a fresh local sandbox.
A transaction investigation pins end-of-block state. A new simulation is a what-if experiment from that state, not an exact replay of the original transaction's pre-state. Behavior comparison does not validate proxy upgrades or storage-layout compatibility.
Import a real project
Use Project workspace to import Solidity files, a folder with dependencies, standard JSON, or Hardhat/Foundry build-info.
Foundry folder imports read literal profile.default compiler, optimizer, EVM, via-IR and remapping settings, plus remappings.txt. Advanced TOML and other profiles should use build-info.
Hardhat configuration is never executed. Import artifacts/build-info/*.json for exact compiler settings. Node modules and Foundry libraries must be included in the imported files. Known OpenZeppelin and forge-std folder layouts receive import remappings.
Select Auto to match pragmas, or an exact bundled compiler. Unsupported versions fail explicitly; pragmas are not rewritten. Source imports are limited to 900 KB; simulation sources to 450 KB and its request to 512 KB.
Share a review
Add a title and annotations, then save locally. Export investigation JSON for a portable source-and-evidence snapshot. Create a portable link for smaller investigations, or download a readable HTML report and print it to PDF from your browser.
Links carry compressed content in the URL fragment; the fragment is not sent to the web server. Anyone with the link can read its content. Shared copies do not update automatically.
Localhost URLs only work where that EVMGlass server is reachable. To share across installations, send the JSON file or use the recipient's EVMGlass origin with the same fragment. Browser storage is limited; the latest 12 evidence entries are retained. Export before clearing site data.
Privacy & provider setup
Source and simulation requests are processed by the Go/Node server. Analysis source is not saved by the server. Explicit investigation saves include source and notes in local browser storage. Reports include the selected source, notes, compiler settings and retained evidence.
Address and transaction lookups contact the configured chain provider; verified source lookup contacts Sourcify, with optional Etherscan fallback. Configure ETHEREUM_RPC_URL, BNB_RPC_URL and optionally ETHERSCAN_API_KEY on the server.
RPC overrides and API keys are excluded from generated investigation reports and saved scenarios. No wallet connection, transaction signing or on-chain submission is involved.
Worked example: WETH
Choose Try WETH on the investigation page. Review the Solidity 0.4.19 source and its provider runtime match. Inspect deposit and withdraw in the project workspace. In pinned simulation, call balanceOf(address) for an existing holder with zero native value. Save a note describing the block and observed return, then export the investigation.
For a self-contained local regression example, use Behavior comparison → Try an authorization regression. The baseline rejects an unauthorized release while the edited candidate can pay out. Replaying the failed rule shows the concrete difference.