# Stack traces

Stack traces in blocktorch are provided as call trace as well as interaction flow visualization. They are accessible in the [log details](/use-cases/searching/logs/log-details.md), the [account abstraction explorer](/concepts/data-sources/account-abstraction-modules.md) and the [step debugger](/use-cases/debugging/step-debugger.md).

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.&#x20;

In the[ Step debugger ](/use-cases/debugging/step-debugger.md)you can also access the smart contract source code along with the stack trace to dig deeper into the data.&#x20;

### Call trace

<figure><img src="/files/g4sfMnb6bB0rOmdqabG9" alt=""><figcaption></figcaption></figure>

&#x20;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&#x20;
* The decoded function signature with the argument types it requires
* The `+` and `-` signs enable you to elapse and expand the tree

### Interaction flow

<figure><img src="/files/h2vRBcNWIOvetrbuXckm" alt=""><figcaption></figcaption></figure>

&#x20;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&#x20;
* 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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.blocktorch.xyz/use-cases/tracing/stack-traces.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
