Tokens

The Token Screen offers detailed insights into all tokens on the TICSScan, including their balances, transactions, market value, and contract details. Users can view token-specific metrics, interact with smart contracts, analyze trends, and filter or sort tokens based on performance or activity. This screen provides transparency and helps users monitor assets, track token behaviors, and make informed decisions.

FR 7.001: Total Tokens

Displays the total number of unique tokens deployed on the chain (e.g., 734). This represents all tokens created and registered on the blockchain, including those used for specific applications or ecosystems.

FR 7.002: Tokens List Section

The Tokens List section provides a detailed table of all tokens deployed on the Qubetics blockchain, offering essential information about each token and its activity. The table includes the following columns:

• FR 7.002a: Token Name Shows the name of the token (e.g., awMTETHBC, ION, INJ) and its connection to a validator or related entity. This helps users understand the token’s purpose and its role in activities like staking or validation within the blockchain network. It provides a clear idea of the token’s identity and its importance in the ecosystem

• FR 7.002b: Contract Address The unique address of the token's smart contract (e.g., 0x47865...46845). Clicking on this address reveals additional details about the token, including its creation history, transaction records, and distribution among holders.

• FR 7.002C: Total Supply Indicates the total number of tokens minted or available for the token (e.g., 1517). This metric provides insights into the token's scale and availability on the network.

• FR 7.002d: Holders Shows the percentage of the total token supply held by various accounts or entities (e.g., 99%). This reflects the token's distribution and concentration, offering insights into decentralization or ownership patterns.

FR 7.003: Pagination

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