> For the complete documentation index, see [llms.txt](https://docs.blocktorch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blocktorch.xyz/use-cases/searching/logs/log-details.md).

# Log Details

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

* `Log type`

<div align="left"><figure><img src="/files/UnALP5nQSBkBgaT2qvcm" alt=""><figcaption></figcaption></figure></div>

* `Transaction hash`

<div align="left"><figure><img src="/files/jIkDD0585BERxEEJbWrq" alt=""><figcaption></figcaption></figure></div>

* `Status`

<div align="left"><figure><img src="/files/Wf7UWBIcN6nL1PKYA5as" alt=""><figcaption></figcaption></figure></div>

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

<div align="left"><figure><img src="/files/Jpb7GmgivxzVTDt4bbez" alt=""><figcaption></figcaption></figure></div>

* `Chain` - you can click the chain name to get redirected to the chain detail page, which can be especially useful in case of [roll-ups](/concepts/data-sources/roll-ups.md) and [local forks](/concepts/data-sources/local-forks.md) to e.g. understand if it is synced with the head of the chain

<div align="left"><figure><img src="/files/7OvRPZXZnMpiMZ4RD5CF" alt=""><figcaption></figcaption></figure></div>

* `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

<div align="left"><figure><img src="/files/XhuL7D7dszgE8PecWSQ5" alt=""><figcaption></figcaption></figure></div>

* `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

<div align="left"><figure><img src="/files/BbBP8IdrfojtwLm4n7Ih" alt=""><figcaption></figcaption></figure></div>

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

<div align="left"><figure><img src="/files/riF5GBQKVxVQSLiSE24A" alt=""><figcaption></figcaption></figure></div>

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

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

* `Transaction Data` - the full decoded transaction data&#x20;

<figure><img src="/files/7s7ltdRgnLb1SXS9hQ5n" alt=""><figcaption></figcaption></figure>

* `Stack trace` - the complete decoded stack trace including gas profiling

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

* `Interaction flow` - the full decoded function invocation flow

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

* `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

From the log details you can also navigate to the [blocktorch transaction step debugger](/use-cases/debugging/step-debugger.md) by clicking the button on the top right, to analyze and debug the specific transaction closely

<figure><img src="/files/4PfdhT2wsKzjTvih4BDX" alt=""><figcaption></figcaption></figure>