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. Searching
  3. Logs

Log Details

Click on a log to expand log details

PreviousLogsNextSharing search results

Last updated 1 year ago

Every single log includes a vast array of detailed information. Blocktorch log details provide information about

  • Log type

  • Transaction hash

  • Status

  • Decoded function signature - if the smart contract ABI is unknown the signature will be anonymous

  • From address - if this is a contract added in your project the name will be displayed, and you can navigate to the contract details page by clicking it

  • To address - if this is a contract added in your project the name will be displayed, and you can navigate to the contract details page by clicking it

  • Timestamp - the format of the timestamp is the time zone of your browser/machine

  • Metrics - out of the box KPIs for this specific function call with a reference to which datapoint this specific transaction is

  • Transaction Data - the full decoded transaction data

  • Stack trace - the complete decoded stack trace including gas profiling

  • Interaction flow - the full decoded function invocation flow

  • L1/L2 tracing - available in the case of roll-up transactions the full trace across L2 and L1

  • Emitted Events - available in case events have been emitted in the transaction an array of emitted events

Chain - you can click the chain name to get redirected to the chain detail page, which can be especially useful in case of and to e.g. understand if it is synced with the head of the chain

From the log details you can also navigate to the by clicking the button on the top right, to analyze and debug the specific transaction closely

roll-ups
local forks
blocktorch transaction step debugger