blocktorch
  • Overview
    • Introduction
    • Install/Setup
    • Quickstart
  • Concepts
    • Data Sources
      • EVM Chains
      • Roll-ups
      • Local forks
        • Setup Hardhat fork
        • Setup managed Hardhat Fork
        • Hardhat forking API
      • Smart Contracts
        • Adding smart contracts
      • Custom Event Data
      • Oracles
      • Account Abstraction modules
        • Navigating the AA Explorer
      • Decentralized Datastorage
      • React Frontends
    • Querying data
    • Telemetry
  • Use cases
    • Searching
      • Logs
        • Log Details
      • Sharing search results
    • Monitoring
      • Building monitors
      • Alerting
    • Tracing
      • Stack traces
      • End-2-End Traces
    • Dashboarding
      • Pre-made dashboards
      • Custom graphs
    • Collaborating
      • Inviting others
      • Sharing data
    • Debugging
      • Step debugger
    • Benchmarking
    • Managing incidents
      • Troubelshooting
      • Post mortem
    • Predicting
  • Ressources
    • Demo videos
    • FAQs
  • Contribute
    • Open Source projects
Powered by GitBook
On this page
  1. Use cases
  2. Debugging

Step debugger

PreviousDebuggingNextBenchmarking

Last updated 1 year ago

Blocktorch's Step Debugger simplifies debugging by providing detailed insights into blockchain transaction execution. It helps identify and solve issues quickly, enhancing your development speed.

Getting started with the step debugger

Navigating to the debugger

To use the Debugger, you need to start from a specific transaction.

  1. Either go to the page from the navigation to choose a transaction or search for a transaction hash in the search bar on top, or click a specific contract in the contract overview to see the contract's logs

  2. Click the 🪲 Debugger button located at the top right of the .

Using the step debugger

The Debugger interface is comprised of three main sections:

  • Execution trace (left): Displays the sequence of calls made during the transaction, , which can be used to navigate through the code.

  • Smart contract source code (top right): Shows the code of the contract being interacted with. If a contract is not added to the project and thus the ABI is unknown we will not be able to show the full decoded data,

  • Call information (bottom right): Provides detailed info about the current call.

Search
log details