> For the complete documentation index, see [llms.txt](https://qubetics.gitbook.io/qubetics-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qubetics.gitbook.io/qubetics-docs/getting-started/tics-scan-user-guide/contract-detail/event-tab.md).

# Event Tab

The Events Tab provides a detailed list of all blockchain events triggered by the smart contract. Events are crucial for understanding contract behavior, analyzing on-chain activity, and debugging issues. This tab helps users track and explore all emitted events in an organized table format.

<figure><img src="https://2711441218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F36u23gOZEZc21qS2BbPV%2Fuploads%2F3NiJs2lRQ4rJVf540qWB%2Fimage.png?alt=media&amp;token=5d0ae90d-06a1-4182-b891-2f46b230f23a" alt=""><figcaption></figcaption></figure>

* **Txn Hash**\
  A unique identifier for the transaction that triggered the event *(e.g., 0x6b5...4c85)*. Clicking on the hash opens detailed information about the transaction, including its logs and execution details.
* **Block**\
  Displays the block number where the event was recorded *(e.g., 187564434)*. This helps users trace the timeline of the event.
* **Timestamp**\
  Shows the time that has passed since the block containing the event was mined *(e.g., 1 min ago)*. This provides real-time context for event timing.
* **Method**\
  Indicates the specific function or method in the contract that generated the event *(e.g., Approval)*. This helps users identify the purpose of the event.
* **Logs**\
  Offers detailed information about the event, broken into:
  * **Topics:** Indexed parameters of the event, such as the sender and recipient addresses or token amounts, which are used for quick filtering and identification.
  * **Data:** Additional non-indexed data associated with the event, providing deeper insights into its details.
  * **Hex View:** A raw hexadecimal representation of the log data, useful for developers conducting low-level debugging or technical analysis.
  * **Dex View:** A decoded and structured representation of on-chain event logs, the Dex View translates raw log data into a human-readable format, making it easier for developers and analysts to interpret smart contract interactions, especially those related to decentralized exchanges or token transfers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://qubetics.gitbook.io/qubetics-docs/getting-started/tics-scan-user-guide/contract-detail/event-tab.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.