> 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.md).

# Contract Detail

The Contract Detail Screen provides a comprehensive view of a specific smart contract deployed on the blockchain. It displays essential information such as the contract’s address, creator, deployment date, and transaction history. Users can explore the contract's type *(e.g., ERC-20)* and its purpose, such as token management, staking, or governance. The screen also includes metrics like the number of transactions, total token supply, and the most recent interactions with the contract. Developers can inspect the contract’s source code *(if verified)*, enabling transparency and trust.

### Contract Details Overview

The Contract Details Overview section provides a summary of key information about a selected smart contract on the Qubetics blockchain. This helps users understand the contract's functionality, history, and activity. Below are the details included:

* **Name**\
  This section displays the contract name, which was kept by the user at the time of contract deployment.&#x20;
* **Contract Address**\
  The unique address of the smart contract *(e.g., 0x20c50ca92f...02C)*. Clicking on this address reveals more technical information, such as its transaction history and interactions.
* **Type**\
  Specifies the type of the contract *(e.g., ERC-721)*, which defines its purpose and the standards it follows, such as for token management or NFT creation.
* **Balance**\
  Shows the current balance held by the contract *(e.g., 400 TICS)*, which could include native tokens or other assets associated with the contract.
* **Creator**\
  Displays the address that deployed the contract *(e.g., 0x47865...46845)*, identifying the entity or account responsible for its creation.
* **Last Executed At**\
  The most recent time the contract was interacted with *(e.g., 15 Feb 2024, 18:15:20)*. This indicates how actively the contract is being used.
* **Deployed At**\
  The time when the contract was deployed to the blockchain *(e.g., 15 Feb 2024, 16:15:20)*, provides context about its history.
* **Internal Transactions Count**\
  Displays the total number of transactions associated with the contract *(e.g., 4)*. This provides insight into the contract's activity level and its usage within the network.
* **Transaction Hash**\
  Displays the hash of the most recent transaction associated with the contract *(e.g., 0x8fdc43...4c8f345)*. Clicking this hash gives more details about the transaction.

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

### Token Information

The Token and Transaction Information section provides comprehensive details about the token associated with a specific smart contract and the transactions linked to it. Here’s a breakdown of the details:

* **Token Name**\
  Displays the name of the token linked to the contract *(e.g., Qubetics)*, making it easy to identify.
* **Symbol**\
  Shows the token's ticker symbol *(e.g., TICS)*, a shorthand representation used in transactions and listings.
* **Decimal**\
  Indicates the number of decimal places the token supports *(e.g., 18)*, defining its divisibility for smaller transactions.
* **Total Supply**\
  Shows the total number of tokens minted or currently available *(e.g., 150M)*, providing insight into the token’s scale and availability.

### Pagination

Pagination controls at the bottom of the contract detail allow users to navigate through multiple pages of token data efficiently (e.g., 1, 2, 3 ... 12).

<br>


---

# 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/contract-detail.md?ask=<question>&goal=<endgoal>
```

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