Avascan Knowledge Base
  • Get started
  • đź“—How to use Avascan
    • Introduction
    • Homepage
    • Unified Transaction List
    • Blocks
    • Assets
    • Token page
    • Verified contracts
    • Marketcap
    • Network Activity
    • Avalanche Bridge
    • Transaction Details
    • Blockchains
    • X-Chain
    • C-Chain
    • Staking
    • Whale Transactions
    • Rich List
    • Hot dApps
    • Burned Fees
    • AVAX Genesis
    • Avalanche Market Cap
    • Keyboard shortcuts
    • Universal Search v0.1
    • Metamask configuration
  • Delegation
    • How to delegate
    • FAQs
    • How to choose a validator
    • Avascan validators
  • 🌟Programs
    • Validator Claim
    • Asset Claim
    • Address Claim
    • The Blue Badge
  • 👩‍💻Tutorial
    • How to verify smart contract
    • How to setup your token marketcap
    • Deploy and verify an ERC-20 token
  • đź“–APIs
    • Documentation
    • /api/v1 (deprecated)
      • Supply (deprecated)
      • Statistics (deprecated)
      • Staking (deprecated)
      • Burned fees (deprecated)
      • GraphQL (deprecated)
    • /api/v2
Powered by GitBook
On this page
  • C-Chain
  • X- Chain
  • Cross Chain Transfert

Was this helpful?

  1. How to use Avascan

Transaction Details

PreviousAvalanche BridgeNextBlockchains

Last updated 3 years ago

Was this helpful?

When clicking or searching for a TX you are redirected to a page that shows various informations. C-Chain and are a bit different, in detail:

C-Chain

  • Transaction id: the identification code of the TX, unique and automatically generated

  • From: the sending address

  • To: the receiving address

  • Burned: the amount of $AVAX burned to process the operation,

  • Status: displays if a transaction occurred positively or not, describing eventually the issues in few words

  • Avax Amount: the $AVAX transferred in the TX

  • Token Transfer: displays the number of token, if present, moved during the operation

  • Block: here you can find few information such as AGE (the date and time of when the TX happened) and HEIGHT (the number of blocks before the one involved in the TX)

  • Transaction Cost: displays in detail the burned $AVAX, the gas fee and the total

  • Internal Operations: displays the number of operations and the details of the addresses, the type of operation, the gas used and the amount of $AVAX transferred from an address to the other

  • Execution Tree: here is a small code explaining the execution order of the internal operations

  • Logs: in full detail the addresses that executed the internal operations

X- Chain

  • Transaction ID: see above

  • Accepted: when the TX got accepted by the Node, it shows full details (date, hour)

  • Burned: see above

  • Status: see above

  • Type: identifies the nature of the TX. Can be a base one ($AVAX from an address to another), token transfert, asset creation, export TX and others

  • Total Imported/Exported: the amount of $AVAX migrated from a chain to another, if the case

  • Inputs: the sending address and the amount of $AVAX sent

  • Outputs: the receiving address and the amount of STXO and UTXO sent back

  • Memo: this is a space that can be filled with a small text providing useful information for the receiver

  • Raw Bytes: a machine representation of a transaction, with the sender' signature attached to it

Cross Chain Transfert

If you are browsing a TX that displays in the output “exported to C-Chain” or “imported from X-Chain” in the input you can click on the available arrow and be redirected to the other TX. If the arrow is not available you'll display a green dot that explains the UTXO is not spent or not spent yet. X-Chain and C-Chain TXs are connected in this particular case. You can find both transaction separately with their ID and you can switch between them to see the complete process of the operations.

đź“—
X-Chain transactions
for more details
Page sample