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
  • Call trace
  • Interaction flow
  1. Use cases
  2. Tracing

Stack traces

PreviousTracingNextEnd-2-End Traces

Last updated 1 year ago

Stack traces in blocktorch are provided as call trace as well as interaction flow visualization. They are accessible in the , the and the .

The stack trace displays the sequence of function calls in a transaction as a tree structure.

Each element represents a function call or event trigger and includes information such as call stack depth, call type, and call parameters.

In theyou can also access the smart contract source code along with the stack trace to dig deeper into the data.

Call trace

The call trace includes:

  • The Calltype which can be CALL, STATICCALL or DELEGATECALL

  • The Gas used shown as whole number in [] and on the right side visualized in blue bars to do gas profiling of each function step

  • The to address of the contract the call was made to

  • The decoded function signature with the argument types it requires

  • The + and - signs enable you to elapse and expand the tree

Interaction flow

The call trace includes:

  • The Calltype which can be CALL, STATICCALL , DELEGATECALL or OTHER , the call types are also visually color coded as the color of the branch

  • The Gas used visualized as the thickness/weight of the branch

  • The to address of the contract the call was made to

  • The decoded function signature with the argument types it requires

  • The round node at each branch can be clicked to elapse and expand the branch

log details
account abstraction explorer
step debugger
Step debugger