> 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/address-detail.md). # Address Detail The Address Details section provides a comprehensive view of a specific blockchain address, including its activities, balance, and participation in the network. This helps users understand the address's role and engagement with the TICSScan. ### **Address** Displays the unique identifier for the address being explored *(e.g., 0xdc3f349f02...c4e9e)*. This is the account or wallet interacting with the blockchain ### Overview * **Balance**\ Shows the total token balance held by the address *(e.g., 1,716.042 TICS)*. This represents the available tokens in the account. * **TICS Value**\ Provides the equivalent monetary value of the token balance in the network’s native currency *(e.g., $1,529,253.97)*, giving users an understanding of the account's total worth. * **Transaction Count**\ Displays the total number of transactions associated with the address *(e.g., 5,245)*. This reflects the address's activity level on the blockchain. ### More Info * **Stake**\ Indicates whether the address is participating in staking. If not staked, it will display as ***"10 TICS"***.This shows whether the account is contributing to network security or earning staking rewards. * **Blocks Validated**\ Shows the total number of blocks validated by the address *(e.g., 5 Blocks)*. This applies to validator addresses and highlights their contribution to maintaining the network. ### Total Transaction Tab Below the high-level address details, the Transaction History table provides a detailed record of all activities associated with the address. The Transactions tab is active by default, but users can also switch to the Tokens tab to explore token-specific details.
* **Txn Hash**\ A unique identifier for each transaction *(e.g., 0x475...4845)*. Clicking on the hash opens a detailed view with additional information about the transaction, such as gas usage and status. * **Block**\ Displays the block number where the transaction was recorded *(e.g., 4675633)*, providing context on when it was confirmed on the blockchain. * **Method**\ Specifies the type of transaction or blockchain interaction *(e.g., Coin\_Transfer)*. This helps identify the transaction's purpose. * **From**\ Displays the sender's address *(e.g., 0x47865...46815)*. If the current address sent tokens. * **To**\ Shows the recipient's address *(e.g., 0x6f6f...453d2)*. If the current address received tokens. * **Timestamp**\ Indicates how much time has passed since the transaction was confirmed *(e.g., 4 days 2 hrs ago)*. This helps users track the timeline of activities. * **Value**\ Reflects the amount of tokens or assets transferred in the transaction *(e.g., 36.62 TICS)*. This indicates the scale of the transfer. * **Status**\ The status column shows the current state of each transaction, indicating whether it is ***"Success"***, ***"Pending"***, or ***"Failed"***. ### Total Tokens Tab The Tokens tab displays all tokens held by the address, offering detailed insights about each token. It also provides a comprehensive overview of an address’s token holdings, enabling users to analyze balances, explore token contracts, and understand the role of validators in token-related activities. The information is presented in a table format with the following columns:
* **Token Name**\ Displays the token name *(e.g., awMTETHBC)*. This provides context on which transaction was made for that particular token. * **Symbol**\ Displays the token's ticker or symbol *(e.g., 512452)*. This is a shorthand representation of the token for easy identification. * **Txn Hash**\ A unique identifier for each transaction *(e.g., 0x475...4845)*. Clicking on the hash opens a detailed view with additional information about the transaction, such as gas usage and status. * **Method**\ Specifies the type of transaction or blockchain interaction *(e.g., Coin\_Transfer)*. This helps identify the transaction's purpose. * **From**\ Displays the sender's address *(e.g., 0x47865...46815)*. If the current address sent tokens. * **To**\ Shows the recipient's address *(e.g., 0x6f6f...453d2)*. If the current address received tokens. * **Timestamp**\ Indicates how much time has passed since the transaction was confirmed *(e.g., 4 days 2 hrs ago)*. This helps users track the timeline of activities. * **Value**\ Reflects the amount of tokens or assets transferred in the transaction *(e.g., 36.62 TICS)*. This indicates the scale of the transfer. * **Status**\ The status column shows the current state of each transaction, indicating whether it is ***"Success"***, ***"Pending"***, or ***"Failed"***. ### Export Enables users to export the transaction history of the address in CSV format, allowing for detailed offline analysis. ### Pagination Users can navigate through multiple pages of transactions using the pagination controls located at the bottom of the table (e.g., 1, 2, 3 ... 12).
--- # 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/address-detail.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.