Practical overview
When it fits
Use it when a visual control-flow view, opcode-level inspection or storage visibility would help investigate Solidity contract behavior, and you can connect it to a node supporting `debug_traceTransaction` for transaction tracing.
Who it is for
- Solidity developers examining contract execution
- Developers tracing transactions across contracts and inspecting their storage or opcodes
Documented uses
- Visualize a contract's control-flow graph and the route taken by a transaction.
- Relate executed opcodes to source snippets and transaction EVM state.
- Inspect runtime or constructor disassembly and contract storage values.
- Follow contract-specific traces for calls made during a transaction.
Requirements & limits
The README documents local startup from source with Git and npm, a Docker Compose option, and a release download. The repository identifies the software as GPL-3.0 licensed.
- Transaction tracing requires a node with
debug_traceTransaction; the README names Geth and Ganache and excludes Infura. - The documented source-mapping and contract features target Solidity.
- Bytecode-only debugging is experimental and does not provide source mappings for CFG operations.
- The default node endpoint is
http://127.0.0.1:8545, with settings for another chain and optional basic authentication.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start the debugger and load Solidity contracts
Run the application locally and load Solidity files from a directory.
Before you start
- Git and npm for the documented source-based setup
- A local directory containing Solidity contracts
Steps
Clone the repository and change into its directory.
Run the command below, then the command below.
npm installnpm startOpen
localhost:9090in a browser.Enter the contract directory path; the application loads Solidity files recursively.
Expected outcome
The interface creates a tab for each Solidity file it finds, with actions available from the file tab's left menu.
Guide limitations
- The README notes that the rewritten application may have new bugs.
Inspect a Solidity transaction trace
Use the graph and execution trace to examine a transaction involving loaded contracts.
Before you start
- Solidity contract files loaded in the debugger
- An Ethereum node that supports
debug_traceTransaction, such as Geth or Ganache - The transaction hash to inspect
Steps
Load the relevant Solidity contract directory in the local interface.
Configure the node endpoint in settings if it differs from the default
http://127.0.0.1:8545; configure basic authentication if the RPC endpoint requires it.Provide the transaction hash for debugging.
Select an opcode on the execution trace to inspect the related source snippet and transaction EVM state.
Expected outcome
The transaction execution is highlighted on the contract control-flow graph, with source and state details available for selected executed opcodes.
Guide limitations
- The node must support
debug_traceTransaction; the README says Infura is not supported. - Only Solidity is supported.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- fergarrui/ethereum-graph-debugger · Official homepage title · retained in its source language