Transaction Details
Last updated
Last updated
The TICS Scan transaction detail page provides all the important information about a specific blockchain transaction. It includes details like the transaction hash (a unique ID for the transaction), the sender and receiver addresses, the amount transferred, gas fees, and the transaction status. This page helps users verify and understand the key components of a transaction, making it easy to track activity and ensure transparency on the Qubetics blockchain.
The overview tab provides a complete breakdown of each transaction on the TICSScan. This information helps users understand the transaction's status, purpose, and impact on the network:
FR 5.001a: Status Displays the current state of the transaction (e.g., Success, Failed, or Pending), confirming whether it was processed successfully.
FR 5.001b: Transaction Hash A unique identifier for the transaction (e.g., 7ccc3c04...28d69f1). Clicking on it allows users to investigate the transaction further or share its details.
FR 5.001c: From Shows the sender’s wallet or account address (e.g., 7ccc3c04...28d69f1), indicating the origin of the transaction.
FR 5.001d: To Displays the recipient’s wallet or account address (e.g., 7ccc3c04...28d69f1), showing where the assets or tokens were sent. For smart contract interactions, this could be the contract address.
FR 5.001e: Block Number Indicates the block in which the transaction was included (e.g., 5124526), providing a timeline for when it was confirmed.
FR 5.001f: Amount The total amount of tokens transferred in the transaction (e.g., 100 TICS), helps users assess the value of the transfer.
FR 5.001g: Age Shows when the transaction was confirmed (e.g., 7h ago, 11-06-2023, 7:43 AM), helping track its execution time.
FR 5.001h: Fee Displays the transaction fee paid by the sender (e.g., 0.01 TICS), representing the cost of processing the transaction on the network.
FR 5.001i: Method Identifies the transaction type or function invoked (e.g., Transfer, Delegate, or Smart Contract Call), providing clarity on the transaction's purpose.
FR 5.001j: Gas Used Indicates the computational power consumed to process the transaction (e.g., 78,045). This metric helps users understand resource utilization and network demand.
FR 5.001k: Event Logs Links to logs generated during the transaction (e.g., Event ID: 5124526). These logs provide detailed insights into events triggered, such as token transfers or contract-specific activities.
The Event Logs section provides detailed information about specific events triggered during transactions on the Qubetics blockchain. These logs are essential for tracking activities like token transfers or contract interactions and offer transparency into transaction-related events. The Logs tab supports multiple entries for a single transaction. Each log entry is presented with the same structure, allowing users to analyze different events triggered during the transaction's execution. Each log entry includes:
FR 5.002a: Address The contract or account address linked to the log entry (e.g., 0x2260fce5e5...c2c599). This identifies the source responsible for generating the event.
FR 5.002b: Name Describes the type or purpose of the event (e.g., Transfer), providing context for the log, such as a token transfer or interaction with a smart contract.
FR 5.002c: Topics Topics act as identifiers, linking the log entry to specific data fields or functions in the smart contract. Organized data points related to the event:
From: The sender's address involved in the event (e.g., 0x59b0e6...b81d3e43).
To: The recipient's address for the event (e.g., 0x7cc130...f8d6795).
FR 5.002d: Hex Displays raw hexadecimal data for specific fields in the log. This low-level information is useful for debugging, verification, or advanced analysis by developers.
FR 5.002e: Value Shows the amount or value associated with the log entry (e.g., 3000549 TICS). This typically represents the transferred amount or any other relevant metric tied to the event.
FR 5.002f: Date Provides the age for when the event occurred, helping users track the timeline of activities.
