> 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/block-details.md).
# Block Details
This screen allows the users to explore detailed information about a specific block or transaction, providing clear and transparent insights into blockchain activity. It is designed to help users understand the key data related to the block and its role in the network. Below is an overview of its components and features.
### Overview Tab
The Block Details section provides a detailed view of the essential information associated with a specific block on the Qubetics blockchain. Each component helps users understand the block's role in the network and its contribution to the blockchain's functionality.
* **Block Hash**\
A unique cryptographic identifier *(e.g., 0x5a2dadad1a5a5d...5f5d)* that acts as a digital fingerprint for the block. This ensures the block’s immutability and secures its data.
* **Block Number**\
Represents the block's height in the blockchain *(e.g., 512456)*, indicating its position in the sequence of blocks added to the chain. Also, the user can now switch between blocks from the next and back arrows next to the block no.
* **Validator**\
The address of the validator responsible for producing the block *(e.g., 0x4fydsyuas3j...8d32)*. Validators are crucial for securing the network, validating transactions, and maintaining its overall integrity.
* **Timestamp**\
The exact time when the block was created *(e.g., 1m ago)*. This helps users track how recently the block was added to the blockchain.
* **Txn Count**\
The total number of transactions included in the block *(e.g., 10)*. This provides insights into the activity level during the block's creation.
* **Parent Hash**\
The hash of the previous block *(e.g., 0x5a2dadad...5f5d)*, linking the current block to its predecessor. This cryptographic connection ensures the blockchain’s continuity and integrity.
* **Transaction Root**\
A single hash that represents all the transactions in a block, created using a Merkle tree. This lets anyone prove that a specific transaction is part of the block, without needing to check the entire list of transactions.
* **Receipts Root**\
The receipts root is the Merkle root of all transaction receipts generated after executing the transactions in a block.
* **State Root**\
The state root is the root hash of the application state trie (Merkle tree) after all transactions in a block have been executed.
### Transactions Tab
The Transaction Details section provides important information about individual transactions on the TICSScan, helping users understand and track their activities.
* **Txn Hash**\
A unique identifier for each transaction *(e.g., 0x47865...46845)*. Clicking on the hash opens a detailed transaction view, showing additional information such as gas used, transaction fees, status *(e.g., success or failure)*, and block inclusion.
* **From**\
The address of the sender *(e.g., 0x47865...46845)*. This is the account that initiated the transaction, transferring funds or assets.
* **To**\
The recipient’s address *(e.g., 0x47865...46845)*. This indicates where the assets or funds are being sent. For smart contract interactions, this may also refer to the contract address.
* **Value**\
The amount of cryptocurrency or tokens transferred in the transaction *(e.g., 120 TICS)*. This provides insight into the transaction's size and significance.
* **Timestamp**\
The exact date and time the transaction was processed *(e.g., 16s ago, Sept 28, 2024 04:14 am)*. It helps users determine when the transaction occurred within the blockchain's activity timeline.
### Pagination
Pagination controls below the table help users navigate through multiple pages of transaction data by selecting specific page numbers (e.g., 1, 2, 3). Additionally, the table can be sorted by columns like value, age, or transaction hash, allowing users to organize the data according to their preferences for easier analysis.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://qubetics.gitbook.io/qubetics-docs/getting-started/tics-scan-user-guide/block-details.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.