# Get started

Welcome to the Avascan Knowledge Base.

### What is Avascan <a href="#what-is-avascan" id="what-is-avascan"></a>

Avalanche is a network of blockchains: such a complex platform requires an easy way to browse it. Blockchains, transactions, validators, delegators, assets and smart contracts are all part of the same picture. The Avascan explorer is the answer: designed to be a one-stop shop, it allows users to browse, and developers to build on its API.

[Check Avascan](https://avascan.info/)

The Knowledge Base includes documentation for user to learn all the features on Avascan and how to use them.

{% content-ref url="/pages/-MQwAlHCIUuS6Qc61le5" %}
[How to use Avascan](/how-to-use-avascan/introduction)
{% endcontent-ref %}

It also includes documentation for the Avascan API that interacts directly with the Avalanche network to retrieve data about blockchains, assets, smart contracts, addresses and transactions.

{% content-ref url="/pages/-MP4plOyTXL2tp\_Qb2eC" %}
[Supply (deprecated)](/api/api-v1-deprecated/avax-supply)
{% endcontent-ref %}

If you don't want or cannot validate, here are some guides to understand how delegation works  and what are the most frequent criteria to bear in mind when choosing to delegate.

{% content-ref url="/pages/-MHWLrYsC1p-Gs63Rxmf" %}
[Delegation](/guide-delegation-avalanche-network/guide-delegation-avax-web-wallet)
{% endcontent-ref %}

And you can also find instruction to apply for our Programs.

{% content-ref url="/pages/-MJS3mvT\_1d6Oe337-F8" %}
[Programs](/programs/validator-claim)
{% endcontent-ref %}

Before being published here, some of the pages, or pieces of them you see here are first published on the [Avascan blog](https://blog.avascan.info).

Enjoy exploring the Avalanche network on Avascan!


# Introduction

How to explore the Avalanche network with Avascan

With Avascan, you can explore the Avalanche network.&#x20;

This is a **deep dive** on how to use Avascan to browse blockchains, assets, validators, smart contracts and transactions on the Avalanche network.

{% hint style="info" %}
While Avascan currently explores X-Chain and C-Chain, it's been designed to easily explore multiple blockchains. P-Chain support is already underway, and more Avalanche chains will be supported as they are deployed.
{% endhint %}

{% content-ref url="/pages/-MQwB\_Tw8f7\_4Kd0aSSq" %}
[Blockchains](/how-to-use-avascan/blockchains)
{% endcontent-ref %}

*More documentation coming soon!*


# Homepage

Every Avalanche data at a glance

Avalanche is a network of blockchains: such a complex platform requires an easy way to browse it. Blockchains, transactions, validators, delegators, assets and smart contracts are all part of the same picture. The Avascan explorer is the answer: designed to be a one-stop shop, it allows users to browse, and developers to build on its [API](/api/documentation).

The home page has several features such as: Pages list, data blocks, Bridge block, Genesis block, Latest transactions block and Latest Whale Transaction block.&#x20;

## Pages list

On the top right you can access easily to the various pages of the site, such as:

* **X-Chain**: for all the information about this page [click here](/how-to-use-avascan/x-chain)&#x20;
* **C-Chain**: this page displays all the trasactions, block and tokens on this very chain in the Avalanche network
* **All Chains**: this page displays all the blockchains active on the Avalanche Network, featuring several informations and data
* **Marketcaps** (Beta): this page displays all the tokens and their relative market cap. In addition you can see the current price and the total supply.
* **Stats**: a page that includes much more such as the whale transactions, the hot dapps page and much more. In other words all the available features in the network.
* **Staking**: for all the information about this page [click here](/how-to-use-avascan/staking)&#x20;

## Search bar

Below the page buttons there is the search bar where you can search dinamically. Our universal search allows searching by type and  the results are sorted by type (ex: token, contract etc). Also Avalanche native tokens are displyed as first results in the search. [For more informations](/how-to-use-avascan/universal-search-v0.1)

## Utility blocks

This section is the core of the homepage, having the informations that generally everybody search about a particoular coin. The informations are updated dinamically to keep the datas fresh, in detail:

* **Blockchains:** the current number of blockchains on the Network
* **Validators**: the current number of active validators
* **Staking ratio**: the percentage of $AVAX staked of the total supply
* **Staking rewards**: an avarage percentage of the various stakes
* **Price**: Current value of 1 $AVAX in USD&#x20;
* **Market cap by circulating supply**: value obtained by the price and the number of tokens circulating
* **Market cap by total supply**: value obtained by adding the market cap of the total projects tokens supply and the market cap of the circulating supply of $AVAX
* **Circulating supply**: number of $AVAX circulating between holders, projects and other
* **Transactions (last 24 hours) X-Chain**: the number of TX in the last day on this chain, [for more details](/how-to-use-avascan/transaction-details)
* **Transactions (last 24 hours) C-Chain**: the number of TX in the last day on this chain
* **Avg TPS (last 24 hours) X-Chain – C-Chain**
* **Avg time to finality X-Chain – C-Chain – P-Chain**: affirmation time needed for a block to be not revocated once committed to the blockchain
* **Gas Price C-Chain**: price in nanoAVAX per unit of gas to pay the fees for different operations
* **Tokens X-Chain – C-Chain**: the total amount of tokens on the network
* **Burned since launch X-Chain – C-Chain**: the toal amout of burned $AVAX, for [more details](/how-to-use-avascan/burned-fees) &#x20;

## Bridge

This section shows the value in USD of the total migrated tokens from others chain to the Avalanche chain. Is a useful tool to look at the market tranding; of course visiting the page you can see all the details. You can browse TXs and tokens to understand better the movement of the supply and of course the relative possibile change of price.&#x20;

## Genesis

In this section few Genesis stats are displayed. The genesis consists in the creation of $AVAX tokens and it is sorted by timelocked or not; also the total supply is displayed. For more details you can visit the [Genesis page](/how-to-use-avascan/avax-genesis).

## Latest transactions

Here are displayed the latest 10 transactions on both C-Chain and X-Chain, the block is updated every few seconds.&#x20;

You can also find the last Whale Transactions (for more info [click here](/how-to-use-avascan/whale-transactions)). Only one is displayed because of course those type of TX happen less frequently than the normal ones.&#x20;


# Unified Transaction List

In this page you can browse all the tx happening on Avalanche. Whether you are new to Avascan or an experienced user, this guide will provide you with the knowledge and tools to understand and navigate transactions effectively.

### Page structure

This page is accessible by clicking from the homepace on **Blockchain** and then **Transactions**.&#x20;

Each type of data has a different tab and you can easily switch betweeen them.

<figure><img src="/files/28qzuDadJ8eWAEckqtWW" alt=""><figcaption></figcaption></figure>

### Transactions

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

In this section you can browse the latest transactions happening inside and outside the Avalanche network system.

The results are displayed in different columns:&#x20;

* **Hash:** or so called Transaction ID, the unique identifier for a transaction, and the subnet in which it was executed
* **Method, if applicable:** the main contract method used in the transaction.
* **Block Info:** the number of the block and the date and hour when the transaction occurred
* **From:** sending address
* **To:** receiving address
* **Value & Fees:** the token and the quantity involved and the fees of the transaction, along with the logo of the subnet in which it was executed

### Internal TXs

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

Internal TXs (Transactions) are operations made inside a transaction that may involve addresses or contracts different that the ones sending or receiving funds. Generally, the more a transactions is complex, the more internal TXs it has.

The results are displayed in different columns:

* **Parent TXN Hash**: The ID of the main transaction
* **Block Info**: the number of the block and the date and hour when the transaction occurred
* **From**: sending address
* **To**: receiving address
* **Value**: the token and its amount, along with the logo of the subnet in which it was executed

### ERC20 TXs

<figure><img src="/files/3HoFSsgvvA9oNNocX8Ca" alt=""><figcaption></figcaption></figure>

This page is similar to the others but here you can only see ERC20 type token transactions.&#x20;

The results are displayed in different columns:

* **Hash:** or so called Transaction ID, the unique identifier for a transaction, and the subnet in which it was executed
* **Age:** how much time ago the TX happened included the date and time&#x20;
* **From:** sending address
* **To:** receiving address
* **Value:** token quantity
* **Token:** the name, logo and symbol of the token involved

### ERC721 TXs

<figure><img src="/files/1OWZxInTE9YS5uOxslu4" alt=""><figcaption></figcaption></figure>

As said above, this page involves only ERC721 transactions.

The results are displayed in different columns:

* **Hash:** or so called Transaction ID, the unique identifier for a transaction, and the subnet in which it was executed
* **Age:** how much time ago the TX happened included the date and time&#x20;
* **From:** sending address
* **To:** receiving address
* **Token ID:** the identificative number of the Token
* **Token:** symbol, name and logo of the token&#x20;
* **Details:** by clicking here on *view NFT* you'll be redirected to the TX page and be able to see the image

### ERC1155 TXs&#x20;

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

Only ERC1155 type token TX.&#x20;

The results are displayed in different columns:

* **Hash:** or so called Transaction ID, the unique identifier for a transaction, and the subnet in which it was executed
* **Age:** how much time ago the TX happened included the date and time&#x20;
* **From:** sending address
* **To:** receiving address
* **Token ID:** the identificative number of the Token
* **Amount:** the quantity of token involved in the TX process
* **Token:**  symbol, name and logo of the token
* **Details:** by clicking here on *view NFT* you'll be redirected to the TX page and be able to see the image


# Blocks

In this page you can browse all the blocks in the Avalanche ecosystem. \
Each block contains a group of transactions and many other data; thrugh cryptographic hashes and the linking of block headers those informations are passed to the next one. <br>

### Page structure

This page is accessible by clicking from the homepage on **Blockchain** and then **Blocks**.&#x20;

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

The results are displayed in different columns:&#x20;

* **Height:** a numerical value that represents the position of a block within the blockchain
* **Age:** how much time ago the operation happened including date and time
* **TXS:** the number of transactions involved in the block
* **Hash:** the unique identifier for the block
* **Gas Used:** the amount of gas spent for the operations
* **Total burned:** the amount of token burned in the process&#x20;
* **Volume:** the volume of gas token used in all the transactions inside the block
* **Size:** the capacity of the block, expressed in bytes
* **Chain logo:** on which blockchain the block has been executed

By clicking on "height" or "hash" in a single row you'll be redirected to another page that includes all the block details with many additional data.&#x20;


# Assets

An asset is a digital rapresentation of a value; this includes everything that can be exchanged, stored and trasferred.    &#x20;

### Page structure&#x20;

This page is accessible by clicking from the [Block ](/how-to-use-avascan/blocks)or [Transaction](/how-to-use-avascan/unified-transaction-list) page and then **Assets**.&#x20;

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

The results are displayed in different columns:&#x20;

* **Type :** asset type
* **Name :** asset chosen name
* **Symbol :** asset chosen symbol
* **Asset ID :** unique identifier
* **Created at :** date and time&#x20;


# Token page

In this page you can browse all the token present in Avalanche network and subnets. Whether you are new to Avascan or an experienced user, this guide will provide you with the knowledge and tools to understand and navigate efficiently.

A token is a value or an asset existing in the chain, to it there is a smart contract associated.

This page is accesible directly from the Homepage by clicking on the Token button available on the top.  &#x20;

### ERC20

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

An ERC20 token is the standard fungible token, this type generated on the Ethereum blockchain but is now used in every chain, included Avalanche. Is the most common token type.\
The results are displayed in different columns:

* **Token:** token name, used chain and icon&#x20;
* **Bridge:** if present, the one use by the token
* **Symbol:** token symbol
* **Dapp:** if present, the one involved with the token
* **Address:** token address
* **Created at:** date and time
* **Market Cap:** total value of the asset

### ERC721

<figure><img src="/files/9MQAElKW9Pr605qum4Sm" alt=""><figcaption></figcaption></figure>

An ERC721 token is the standard non-fungible token,  this type generated on the Ethereum blockchain but is now used in every chain, included Avalanche. &#x20;

The results are displayed in different columns:

* **Token:** token name, used chain and icon&#x20;
* **Symbol:** token symbol
* **Address:** token address
* **TX hash:** or so called Transaction ID, the unique identifier for a transaction, and the subnet in which it was executed
* **Created at:** date and time
* **Details:**  by clicking here on *view NFT* you'll be redirected to the token page and be able to see the image and many other informations

### ERC1155&#x20;

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

An ERC1155 token can be fungible or non-fungible, its key feature is that a single smart contract supports the creation for both types.  This type generated on the Ethereum blockchain but is now used in every chain, included Avalanche.&#x20;

The results are displayed in different columns:

* **Token:** token name, used chain and icon&#x20;
* **Symbol:** token symbol
* **Address:** token address
* **TX hash:** or so called Transaction ID, the unique identifier for a transaction, and the subnet in which it was executed
* **Created at:** date and time
* **Details:**  by clicking here on *view NFT* you'll be redirected to the token page and be able to see the image and many other informations

### &#x20;<br>


# Verified contracts

In this page you can browse all the contract verified on C-chain.&#x20;

A verified contract has its sourcecode reviewed successfully in terms of security, bugs and issues.  &#x20;

You can verify your contract [here](https://avascan.info/blockchain/c/contract/verify)

### Page structure

This page is accessible by clicking from the homepage on **Blockchain** and then **Verified contracts**

<figure><img src="/files/3fZytR5C6dshg7fK0bBt" alt=""><figcaption></figcaption></figure>

The results are displayed in different columns:

* **Address:** asset address
* **Contract name:** name of the asset
* **Version:** the version of contract's code language used
* **TXS:** how many TXs involving this asset happened&#x20;
* **Setting:** you can see two icons, a lightning and a wrench which respectively represent *Optimization enabled* and *Constructor arguments*

<div align="left"><figure><img src="/files/O5egQDc4Q3QMBU9AVthw" alt=""><figcaption></figcaption></figure></div>

* **Creator:** if present, the address that created the contract &#x20;
* **Created at:** date and time&#x20;
* **Verified at:** date and time&#x20;
* **TX hash:** or so called Transaction ID, the unique identifier for a transaction, and the subnet in which it was executed


# Marketcap

In this page you can browse all the [ERC20 tokens](/how-to-use-avascan/token-page) present in the Avalanche network (native or bridged) ranked by market cap value.&#x20;

Market cap, short for market capitalization,  is the misuration of the total value of an asset expressed in USD. &#x20;

The number is obtained with the following calculation: current token price multiplied by total circulating supply.&#x20;

### Page structure&#x20;

This page is accesible directly from the Homepage by clicking on the [Marketcap](https://avascan.info/blockchain/all/marketcap) button available on the top. &#x20;

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

* **Rank:** position in the table, from the highest to the lowest
* **Token:** name, brief description, logo and the involved chain &#x20;
* **Symbol:** token symbol
* **Address:** token address
* **Created at:** date and time
* **Price:** current token price, expressed in USD
* **Supply:** current token supply, expressed in millions
* **Market cap:** current token marketcap, expressed in USD. By clicking on the icon next to it you'll be redirected to GeckoTerminal liquidity pool (if present) &#x20;


# Network Activity

In this page you can monitor all the network activity happening in the Avalanche ecosystem. \
You can filter the datas by chain (including subnets) and browse different statistics.&#x20;

This page is accessible by clicking on **Resources** and then **Network Activity**

The page sections are:&#x20;

### Blockchain Data

* **Daily Transaction Count:** this graphic shows the number of transaction happening daily on the chain you selected. The number of TX is an important metric to determinate the daily ufe ot the network. You can see the date and the number for each day scrolling with the cursor.
* **Daily Block Count:** this graphic shows the daily number of blocks generated on the chain you selected. The number is importat to monitor the daily activity, is a crucial metric to see if the chain is working. You can see the date and the number for each day scrolling with the cursor.

### Addresses Data

* **Daily Active Senders:** this graphic shows the daily number of addresses sending to others on the chain you selected. Is an important metric to determinate the amount of usage of the chain. You can see the date and the number for each day scrolling with the cursor.
* **Daily Active receiver:** this graphic shows the number of transaction happening on the chain you selected. You can see the date and the number for each day scrolling with the cursor.
* **Daily Active addresses:** his graphic shows the number of transaction happening on the chain you selected. You can see the date and the number for each day scrolling with the cursor.

### Gas & Fees Data

* Daily Burned fees: his graphic shows the number of transaction happening on the chain you selected. You can see the date and the number for each day scrolling with the cursor.
* Avarange Gas Price: his graphic shows the number of transaction happening on the chain you selected. You can see the date and the number for each day scrolling with the cursor.


# Avalanche Bridge

In this page you can receive information about the Avalanche Bridge; if you want to know all about it visit this [link](https://bridge.avax.network/login).

On the top left the AB address is displayed; on the top right there are 3 useful buttons:

* **TXs on Avalanche:** all TXs involving the Bridge on the Avalanche side are listed in this page. Info about the page layout can be found in the Avascan [C-chain guide](/how-to-use-avascan/c-chain)
* **TXs on Ethereum**: link to the Etherscan page of the Bridge, with the TXs happening on the Ethereum side
* **bridge.avax.network:** link to the official Bridge site and the tool to convert the old bridged tokens with the new ones

Below the address there is the following graphic representing the bridge to Avalanche and the total USD amount bridged toward the Avalanche network.

![](/files/AiN6iWuolvOLbQWf7V3N)

Next, the total number of bridged tokens and info about them is displayed in the following columns:

* **Name:** Token name, symbol and icon
* **Contract address:** Avalanche token contract (not to be confused with the native one)
* **Bridged cap:** market cap of the bridged supply
* **Native price:** current token value (from Coingecko)
* **Bridged supply:** the current amount of tokens locked on the Ethereum side and made available on the Avalanche side through the Bridge (i.e. the total supply available on the Avalanche network)


# Transaction Details

When clicking or searching for a TX you are redirected to a page that shows various informations. C-Chain and [X-Chain transactions](/how-to-use-avascan/x-chain) 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, [for more details](/api/api-v1-deprecated/fees)
* **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

![](/files/DcD8WnHeuyLwe9UgG7IE)

* **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&#x20;

## X- Chain

![Page sample](/files/Je1qmXfJ58WBKXKRZdMp)

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

![](/files/nyAlKXJSpn9kq14fjV68)

![](/files/6inYjsuT2yJ8aMueOO6r)


# Blockchains

Browse blockchain on Avalanche network with Avascan

A **blockchain**, or a chain is defined by a Virtual Machine (*VM*) and a set of validators (*subnet*). Three chains are available at launch:

* **P-Chain**: "platform chain", it manages the Avalanche network
* **C-Chain**: "contract chain", an Ethereum-like blockchain for smart contracts; for more [info](/how-to-use-avascan/c-chain)
* **X-Chain**: "exchange chain" default chain for asset transfers; for more [info](/how-to-use-avascan/x-chain)

Every main chain has a *characteristic color* that lets users understand how assets move between chains. You can search any chain by:

* Entering the *chainID* in the search bar
* Clicking on the **ALL BLOCKCHAINS** link in the navbar
* Click on the **BLOCKCHAINS** box in the left column at the center of the home page.

The last two options will bring you to the **complete list** of the blockchains deployed on the network.

![Blockchains list on Avascan](/files/-MR-LlrHJcAPi_JQ1OoG)

By default, Avascan shows all chains validated by the **Default Subnet**, but clicking on the *Change* button will show a list of all available subnets, filtering the list of blockchains by the subnet that validates them. To show only the blockchains validated by the **Default Subnet**, click on the *Show Default Subnet* button.

![Blockchain Details page on Avascan](/files/-MR-L82wAhxHUZOYaF4Y)

To enter the **Blockchains Details** page, simply click on a list item. The Blockchain Details page shows:

* **Blockchain ID** (except P-Chain)
* **Name**
* **Alias**
* **Status** of indexing on Avascan (i.e. if you can search assets, addresses transactions and/or smart contracts on it)
* **Virtual Machine**
* **Consensus protocol**
* The related **Subnet**, along with subnet ID and total number of validators.

### [Browse the blockchains on the Avalanche platform](https://avascan.info/blockchains)


# X-Chain

X-Chain indexing is provided by Norge, Avascan's powerful custom Avalanche indexer.

At time of writing, X-Chain is the most completely indexed chain among the chains validated by the **Primary Network**. X-Chain indexing is provided by **Norge**, Avascan’s custom indexer now in version 1.0, announced in our [Explore #11 newsletter](https://blog.avascan.info/2020-12-04-explore-eleven.html) in late 2020.

Data about X-Chain is accessible by clicking on the **X-Chain** button in the navbar. Currently, all aggregated data and the transaction list shown in the home page show data from X-Chain only.

![Transation on X-Chain on Avascan](/files/-MRzJj9Ob1uEzxn-1iEj)

The *Transactions on X-Chain* page shows basic information about X-Chain: its **name** and **blockchain ID**, as well as a list of transactions and assets on-chain, that are displayed in two tabs that can browsed by clicking either the **TRANSACTION** or the **ASSETS** button in the right side of the page. By default, the **TRANSACTIONS** tab is shown first.

*More coming soon!*


# C-Chain

C-Chain is one of the three chain in the Avalanche network, a short for “Contract Chain”. It is the chain dedicated to the creation of Ethereum-compatible smart contract. It is currently the most populated and complex.

The C-Chain page on Avascan is divided in three sections:

* **Transactions**
* **Blocks**
* **Tokens**

## Transactions

Top left of the page you can see the current total number of transactions on the chain.

You can filter results by:

![](/files/6LW6oaDPyluUVGQcCL6Q)

* **TX type:** Import (TXs bridging in from X-Chain) , Export (TXs bridging out to [X-Chain](/how-to-use-avascan/x-chain)), ERC20 (TXs involving the trasfer of ERC20 tokens), ERC721 (TXs involving the trasfer of NFTs)
* **Time span:** it is possible to only show txs occurred during a certain time span

The following columns are displayed as results:

* **Hash:** here you can see the TransactionID and the TX sender and receiver
* **Block Age:** how long ago the TX happened and the date and hour of the event
* **Avax Amount:** the amount of $AVAX involved in the TX
* **Status:** represented with three icons Success, Failed or Reverted

![Success; Failed; Reverted](/files/MNZZIqmnBKLqrWD0akal)

&#x20;

## Blocks

Top left of the page you can see the current total number of blocks on the chain

You can filter results by **time span** (already explained above)

The results are displayed in few columns:

* **Height:** the number of blocks before the one involved in the TX
* **Age:** how long ago the block has been accepted onto the chain, with date and hour as well
* **Transactions:** the number of TX in the block
* **Gas used:** gas used in the block
* **Total burned:** the amount of $AVAX burned in the block
* **Volume:** the amount of $AVAX transferred in the block
* **Size:** the width of the block expressed in bytes

## Tokens

In this page you can switch between **ERC20** and **ERC721**; visiting the relative page you can see the total number of tokens present on the Avalanche chain.

You can also filter results switching on and off the **Bridged** button in the ERC20 page in order to show the bridged one only.

The results are displayed in the following columns:

* **Name:** smart contract name
* **Contract address**
* **Created at**: the date and time of the token creation
* **Total supply**: for bridged or multichain tokens, this number only refers to the supply in the Avalanche network


# Staking

Browse validators and delegations on the Avalanche network with Avascan

This page is the one to look if you want to track all the staking process: both Validators and Delegations informations on the Avalanche Network are displayed here. If you are doing one of those, or planning to: this is your place.

&#x20;To help you starting you can also check **our guides** including:

* [How to choose a Validator](https://docs.avascan.info/guide-delegation-avalanche-network/choose-validator-node-avalanche)
* [How to delegate](https://docs.avascan.info/guide-delegation-avalanche-network/guide-delegation-avax-web-wallet)
* [Staking FAQ](https://docs.avascan.info/guide-delegation-avalanche-network/faq)

And also know our [Validators](https://docs.avascan.info/guide-delegation-avalanche-network/avascan-validators).

The page is divided in two main sections: Validators and Delegations. In both sections you can **Calculate the delegation reward** and see the **Staking stats**. And also choose the numbers of rows displayed per page.

![](/files/-MlEr3Czvg4DMiLom-uf)

## Calculate delegation reward

This calculator will automatically display in the three bottom sections the amount of your rewards. The rewards are expressed in: **net rewards** such as the amount of $AVAX you are going to receive; the **percentage of yield** is going to be allocated and the difference through time. You can enter the **amount of $AVAX** you are planning to delegate and the **delegation fees**; you'll obtain precise results.

![](/files/-MlErOidmAxk5J20rphc)

Validators

&#x20;In this section you can filter all the data by:

* **Free space** entering the amount of $AVAX you'll see all the validators that have at least that free space available (for example: if you enter "10 $AVAX" as a filter all the nodes that have 10 $AVAX, 11 $AVAX, 12 $AVAX etc will be displayed)&#x20;
* **Time left** selecting: any, 2 weeks, 3 month, 6 months and 9 months you'll see all the validators that have at least that time left (for example: if you enter "2 weeks" as a filter all the nodes that have 2 weeks left, 3 weeks left etc will be displayed)&#x20;
* **Fee** selecting: any, 2%, 5%, 10% and 20% you'll see all the validators with that maximum that fee (for example: if you enter "10%" as a filter all the nodes with 10%, 5% and 2% will be displayed) &#x20;
* **Max yield** selecting: any, 1%, 3% and 5% you'll see all the validators that have at least that much yield.&#x20;
* **Good uptime** by turning it on and off you'll see all the validators with at least 90% uptime observed by 30 nodes in the network
* **Claimed** by turning it on and off it will display the nodes associated with a defined identity (the ones with alias, manager and/or an icon claimed via our [Validator Claim Program](https://docs.avascan.info/programs/validator-claim))

![](/files/-MlEtJ1Jp3x7FOkaPoGS)

The total **number of active validators** is available in the top left and is always updated. The rows are displayed by:

* **Node** here you can find the ID, manager, alias and icon
* **Total stake** the amount of $AVAX currently staked both by the validator's owner and all the delegations
* **Free space** the amount of $AVAX the node can still support
* **Delegations** number of delegations
* **Start date**
* **Time left** for the validation to end
* **Fee amount**
* **Max yield** if you start delegating now until the end

![Validators page columns](/files/-MlEuIXr95Fs40RE1Uo0)

## Delegations

The total **number of active delegations** in available in the top left and is always updated. The rows are displayed by:

* **Beneficiary** the address who is delegating
* **Delegated node** the chosen validator
* **Delegated** the amount of $AVAX
* **Started on** the starting date
* **Time left** for the delegation to end

![Delegations page columns](/files/-MlF3fnULiHoVR2uuLv2)


# Whale Transactions

Browse the latest and top transactions over 100,000 AVAX

This section is a part of the Stats page and it shows all the so called Whale transactions: in other words all the transaction on the Avalanche network over 100,000 $AVAX

Those big transactions always alarm users for many reasons:

* Is relevant to know how big holders are moving funds across the network
* Could be made by a project moving timelocked funds, pools funds
* Could move significantly $AVAX price
* Could be part of an exploit, a rug pull or some other scam

The more you know the safer you are, that's why we decided to make this section, to monitor all the activity and be able to take action, if is needed.

## Page structure

The section is divided in other two sections: **Latest 100** and **Top 100.**

![](/files/zRIcnXAGSyEl3V1ra5aj)

Displaying only 100 will keep updated daily and help the investors to stay focused on the movements happening on the chain.

You can filter the displayed datas by **all** chains, [**X-Chain**](/how-to-use-avascan/x-chain) and **C-Chain.**

![the chain filters](/files/6oN2QDk7G3WQEHENTs1D)

![displayed columns](/files/p4MqJsRpmJyMIypSDQSy)

The columns where the datas are displayed are divided by:

* **From:** the sending address
* **To:** the receiving address or the smart contract interacted with
* **Created at:** date and hour of the transaction
* **Amount:** number of $AVAX transferred
* **Value:** total value in the current $AVAX price

If you want to know more about TX [visit this guide](/how-to-use-avascan/transaction-details).

{% hint style="info" %}
We currently only support whale transactions executed with AVAX as the main token transferred. We will support more tokens in the future.
{% endhint %}


# Rich List

Top addresses by AVAX balance

This section is a part of the Stats page and shows the top **100 rich addresses** in the Avalanche network. It is useful to control those addresses because their activity sure moves the whole market significantly. Of course this section is in combo with the [Whale Transaction](https://docs.avascan.info/how-to-use-avascan/whale-transactions) one and checking both you can manage to invest safer and in a more clever way.

## Page structure

You can filter the data by chain: selecting all, [X-Chain](/how-to-use-avascan/x-chain) and [C-Chain](/how-to-use-avascan/c-chain)

![](/files/6oN2QDk7G3WQEHENTs1D)

The results are displayed in different columns

![](/files/SfSONDKV9FeBVHgxE2Fs)

* **Chain:** X or C
* **Address:** if claimed with the [address claim program](/programs/address-claim) you'll see the Alias
* **AVAX Balance:** the amount of $AVAX the address has and the current value in USD
* **% of Circulating:** the percentage of the total $AVAX supply that this address holds


# Hot dApps

Discover the most used dApps in the last 7 days

Checking the market trend is one of the most important things to do when investing in crypto (or investing in general). By looking the movements of the people you can invest in projects that are going up and abandon the one going down to maximize your income. With our page we inform you which one are the most used Dapps on the Avalanche network helping you to choose where to put your money in.

## Page structure

The page is a section of the Stats one; it shows the top 10 dApps weekly. The criterion for the choice is the number of TX that a single project accumulate; of course there is no permanent position, everyone can go up and down or even disappear from the list.

![column display](/files/C6qTMD1rQMd7xzxdUL2w)

The data are displayed by:

* **Name:** Name of the dApp if registered with our [asset](/programs/asset-claim) and/or [address ](/programs/address-claim)claim program
* **Type:** identifies the nature of the project&#x20;
* **Address**
* **TX Count:** the total amount of [TX](/how-to-use-avascan/transaction-details) done by this dApp in the last 7 days


# Burned Fees

With the term “burned fee” (or "gas fee"), in the blockchain field, we refer to the cost necessary to cover the transaction operation. In other words: the more transactions happen, the more the burned fees amount increase and this shows how active a network is and how much is growing. For more information about the cost and others, you can check the [Avalanche Docs official page](https://docs.avax.network/learn/platform-overview/transaction-fees).

## Page Structure

This section is a part of the Stats page and it shows all the $AVAX burned on C-Chain and X-Chain. In the upper half of the page you have the available **data filter** and a **chart**.

The **data filter** is also applied to the bottom half of the page (explained further) and is divided by:

* **Chain:** by selecting all, C-Chain and [X-Chain](/how-to-use-avascan/x-chain)

![Chain data filter](/files/6oN2QDk7G3WQEHENTs1D)

* **Time:** by selecting 24 hours , 7 days, 30 days and all

![Time data filter](/files/pgKWrcrUXKcgw6Lro0WI)

The **chart** shows:

* The **amount of $AVAX** in the Y axis (the vertical one)
* The **time** in the X axis (the horizontal one).

The amount and the time display changes base on the time lapse you select, recalculating the burned fees in that timeframe.

Below the chart you can find a bar showing the top stats of fees burned on C-Chain and X-Chain.

## Burned fees on X-Chain

In this section you can see the burned fees divided by **transaction type**:

* **Send**: the transactions between addresses
* **AVAX export**: fees used to export assets from X-Chain to P-Chain or C-Chain
* **AVAX import**: fees used to export assets from P-Chain or C-Chain into X-Chain
* **Create Asset**: the process of creation of a new asset (that can be claimed via our [Asset Claim Program](/programs/asset-claim))
* **Mint Asset**: the generation of the shares in a previously created asset (such as an NFT, for example)

## Top C-Chain Addresses&#x20;

Here are displayed the top 5 addresses by burned fees, you can track their activity and see their alias (if registered with our [Address Claim Program](/programs/address-claim)). This section will show the top ones of the time lapse you selected earlier.

## Top C-Chain Contracts

Here are displayed the top 5 contracts by burned fees, you can track their activity and see their alias and icon (if registered with our Program). This section will show the top ones of the time lapse you selected earlier.


# AVAX Genesis

In this page you can see the total $AVAX supply generated on mainnet at launch (360 M $AVAX, the so called “Genesis event”). This supply is divided in two branches:

* **Timelocked**: those tokens are still under vesting conditions and will be unlocked each in a scheduled time
* **Not timelocked**: those tokens are part of the circulating supply and can freely circulate in the market

So: Unlocked $AVAX from the genesis event + Staking rewards to Validators - Burned fees= Circulating supply&#x20;

## Genesis Unlock

In this graphic a preview of the unlocking pattern scheduled through the years for all the generated $AVAX in the Genesis event (already explained above). In the Y axis there is the amount of $AVAX by M, in the X axis the time divided by years. If you move your cursor on it you can see the total amount unlocked per quarter.

![](/files/71qFae07gFToJcxJdxDj)

## Genesis Allocation

This section explains in full details the division of the token by: **Sale**, **Bounties**, **Team** and **Ecosystem**. Giving the user a general idea of not only the number of $AVAX but their relative structure.

**Sale**

* **Seed Sale**: the first ever $AVAX sale
* **Private Sale**: the second main $AVAX sale
* **Public sale option A1/A2**: open to the public
* **Public sale option B**: open to the public

**Bounties**

* **Airdrop**: various and separate airdrop to generate awareness towards Avalanche
* **Denali Testnet Incentive Program**: testnet programs

**Team:** those funds are allocated to the various team members of Ava labs

**Ecosystem**

* **Foundation**: allocated to the Avalanche Foundation
* **Strategic partners**: for all the business companies involving Avalanche
* **Community and developer edowment**: the dev core of the network


# Avalanche Market Cap

Aggregating all tokens on the Avalanche network

Introducing one of the biggest changes since the launch of Avascan: the [Avalanche Tokens List](https://avascan.info/tokens).

This new token list **aggregates all the tokens on** [**X-Chain**](/how-to-use-avascan/x-chain) **and C-Chain**. This list is part of a series of changes that will make Avascan future proof, as Avalanche continues to expand and new blockchains and subnets will make their way in the network.

Since this is in beta, you will see changes to this page almost every week, whether new price feeds are added, the layout is adjusted or new tokens are mapped.

The Avalanche Tokens List aims to be the **go-to list** for everyone that wants to have a complete vision on the total market cap of Avalanche.

![The Avalanche Tokens List](/files/-MlPQCVnTUBtffQE8DJ7)

This is different from what you see on CoinGecko or Coinmarketcap, because here you will only see the actual market cap present in the network, whether it is for native or bridged tokens.

Tokens are sorted by **market cap** and will be sorted again by Blue Badge within the end of the month. If you want to see your token high in the list, it needs a **Blue Badge**. See our new [docs page](/programs/the-blue-badge) to understand more about what’s that and how to get it.

We will have a beta period of about three months, in which we will study how users browse the list, how they use it, and how can we make it the perfect destination for all users to analyze tokens on Avalanche.


# Keyboard shortcuts

If you're a geek like us, you'll enjoy Avascan keyboard shortcuts.

The following are few little hacks that will help you browse faster Avascan.&#x20;

| Shortcut | Description                                                                           |
| -------- | ------------------------------------------------------------------------------------- |
| Tab      | Browse between UTXOs, scroll transactions and navigate through the elements of a page |
| Enter    | Click to enter the details of the element                                             |
| /        | Search using the global search engine for Avalanche                                   |


# Universal Search v0.1

Search addresses, tokens, NFTs, validators and delegations across the Avalanche network

It’s basically the first step towards a universal search for anything on the Avalanche network, starting with the Primary Network.

When you search for a contract, token, or address, Avascan will show the most relevant results. The search algorithm works as it follows: it searches the keyword on NodeIDs, [delegator](/guide-delegation-avalanche-network/guide-delegation-avax-web-wallet) and [validator](/guide-delegation-avalanche-network/choose-validator-node-avalanche) beneficiary addresses, [token](/how-to-use-avascan/avalanche-tokens-list) and [dapp](/how-to-use-avascan/hot-dapps) names, along with other IDs, looking for partial matches too.

![Search results looking for 'usd'](/files/-MlPw2lp08EkGT6qshl_)

Then the magic happens: we combine **all tokens on a single list**, describing which chain they’re on, and sort addresses, tokens and smart contracts by their alias or name. For tokens, we sort them again by market cap, and then we sort this whole result by Blue Badge check.

![Blue Badge in search results](/files/-MlPwGC1Hj2J-6cEJqfi)

The Blue Badge is basically a verified badge (very familiar to what you see on other explorers or even on social networks) that we give to projects that we know very good.

We are rolling out the Blue Badge to new projects’ contracts and addresses every week. See our new [docs page](/programs/the-blue-badge) to know more about it. With this algorithm, the search is going to get better and better, as we get more token prices and more data about addresses and tokens.


# Metamask configuration

Configuration of Avalanche C-Chain on Metamask

## On desktop

Go on “Networks” and select Custom RPC

![](/files/-Mf8HevEjOnb_FVCiMPK)

Enter the following details:

* **Network name**: Avalanche
* **New RPC URL**: <https://api.avax.network/ext/bc/C/rpc>
* **Chain ID**: 0xa86a
* **Symbol**: AVAX
* **Block explorer URL**: <https://avascan.info/blockchain/c/>

![](/files/-Mf8Hn6IhD1pExST2TOa)

### On mobile

Go on “Settings” > “Networks” > and select “Add Network”

![](/files/-Mf8YJ3SDfOM9DpKnuH0)

![](/files/-Mf8YMXnNergTUg5ncLv)

![](/files/-Mf8YRNQ866oPuyN8SLh)

Enter the following:

* **Network name**: Avalanche
* **New RPC URL**: <https://api.avax.network/ext/bc/C/rpc>
* **Chain ID**: 0xa86a
* **Symbol**: AVAX
* **Block explorer URL**: <https://avascan.info/blockchain/c>

![](/files/-Mf8YVHmzlfgyJvq5aki)

Then click "Add".


# How to delegate

How To delegate your AVAX and earn up to 12% yearly in staking rewards

### Introduction: X-Chain and P-Chain

The[ **X-Chain**](/how-to-use-avascan/x-chain) acts as a decentralized platform for creating and trading smart digital assets. (Think X for eXchanging *assets*). Another chain inherent to the Avalanche network is the **P-Chain**, which manages metadata about the Avalanche network. (P stands for *platform*).

As an AVAX presale participant, you will receive your tokens in your P address (90% of option A1 or option A2) and/or X-Chain address (Option B and 10% of yout tokens if you purchased option A1 or A2).

An **X address** is an address created on X-Chain, the main asset chain on the Avalanche network. Tokens held in X addresses are liquid, meaning that they can be freely transferred to other X addresses and to P addresses.

**P addresses** are addresses created on P-Chain, the platform chain on the Avalanche network. Tokens held in P addresses may be illiquid, meaning that you may not be able to move those tokens freely to your X address. You also cannot move your tokens from one P address to another directly, but you need to transfer the tokens to an X address first.

AVAX held in P addresses may be **vested (locked)** (from the genesis allocation on mainnet) or **staked** (via validation with a full node, or delegation).

This guide will help you get through the delegation of your AVAX tokens to a validator, helping you choose which is best for you.

### Access your web wallet

The first step is to, obviously, access your AVAX Wallet. You can access it from [here](https://wallet.avax.network). If you haven't created one already, you can follow the step-by-step creation by clicking on the **'CREATE NEW WALLET'** button.

### Transfer to P

{% hint style="info" %}
Most users have received 90% of AVAX purchased in the P address. if you're one of them and you want to only delegate your **locked** AVAX, you can simply skip this step. If you also want to delegate your unlocked AVAX, you can proceed here to transfer them to P as well.
{% endhint %}

![AVAX Wallet Dashboard](/files/-MHWgWWRxDhSBgT1oaWO)

To stake AVAX (by validating with your node or delegating another node in your place), you need to first transfer the amount of AVAX you want to stake to P-Chain.

Click **'Earn'** on the right sidebar, and then click the **'TRANSFER'** button.

![AVAX Wallet Earn page](/files/-MHWgemBI5IjX4KYVVTX)

Make sure you transfer the amount you want to stake **plus 0.001 AVAX**, that is the fee that you will pay to do the transfer between the chains. Click again on **'TRANSFER'** to confirm. And keep in mind that the minimum amount to[ stake](/how-to-use-avascan/staking) in delegation is 25 AVAX, so make sure you transfer *at least* **25.001 AVAX** from X to P.

![AVAX Wallet Cross Chain Transfer page](/files/-MHWgnvySsKDOB3Qr8ol)

### Add delegation to a validator

Now that you have your AVAX in your P-Chain address, you're ready to stake by delegating!

Return to the 'Earn' page, then click on **'ADD DELEGATOR'**.

![AVAX Wallet Earn page](/files/-MHWh5dXRA6kpmB_LGyb)

You will be presented with a list of validators ordered by the total amount staked.

![AVAX Wallet Delegate page](/files/-MHWhHVroMfWE8sz0VeB)

### Select your validator

Once you've [chosen your validator,](/guide-delegation-avalanche-network/choose-validator-node-avalanche) you can then **'SELECT'** it.

![AVAX Wallet Delega page - Select Node](/files/-MHWhXOpzH6WeBHB5hca)

You're then presented with the delegate page. You can choose the **staking period** (remember: you cannot stake longer that your validator's), the **amount** that you want to delegate in stake and specify the **reward address**, if you don't want to receive rewards on the same address from which you're staking.

![AVAX Wallet Delegate page - Confirm Delegation](/files/-MHWhelGH0DAvxN3-2CK)

When you've entered all the information, you can just press **'CONFIRM'** to confirm the data you input, and then **'SUBMIT'** to confirm the delegation.

![AVAX Wallet Delegate page - Submit Delegation](/files/-MHWhu8Gf9hl0ayBCxmv)

You're all set, now *you're delegating*!

### Get support

If you want to get continued support and want to know more about delegating and validating on the Avalanche network, join our [Telegram chat](https://t.me/AvascanExplorer).


# FAQs

We’re constantly expanding these FAQs: new ones are first

### Rewards earned from delegating locked tokens are unlocked tokens or also locked tokens?

Rewards are always transferred as unlocked tokens.

### I keep trying to delegate and I get confirmation on AVAX wallet, but the delegation doesn't show and my balance doesn't change, what should I do?

This may be a compatibility issue. If you're running on Chrome, try switching to Microsoft Edge or Windows or to Safari or Firefox on macOS.

### What's the maximum staking duration?

For both validating and staking, the maximum duration is 1 year.

### What's the minimum staking duration?

For both validating and staking, the minimum duration is 2 weeks.What's the maximum amount that a validator can accept in delegations?

A validator can accept 4 times its validation stake up to 2.4 million AVAX. For example: a node with a 10,000 AVAX of validation stake can accept 40,000 AVAX for a totale stake of 50,000.

### Is staking reward paid on a daily basis?

No, rewards are paid at the end of the staking period.

### How long does my validator need to stay online for me to get rewards?

Validators are required to have a minimum of 80% uptime on mainnet to earn full staking rewards.

### **What happens if my validator goes offline?**

If your validator goes offline you lose your potential staking rewards, and your AVAX will remain locked until the end of the delegation period.

### **Is there slashing in Avalanche?**

No, validators (and hence their delegators) are not slashed for bad behavior.

### **Is there a minimum amount of AVAX required to delegate?**

Yes, the minimum amount is 25 AVAX.

### **Can I delegate with my Ledger?**

Yes, you can, directly from the web interface. We'll publish an How-To in the coming days.

### **On which chain are my vested AVAX?**

Vested AVAX are transferred to your P address with time-locked outputs. When the time-lock expires (at the end of the vesting period), you can transfer AVAX to your X address using the Cross Chain Transfer feature in the web wallet.

### **Will the AVAX I purchased be allocated on X-Chain or P-Chain?**

Vested AVAX (option **A1** and **A2**) will be distributed on P addresses, while unlocked AVAX (option **B** and some from option **A1** and **A2** on mainnet launch) on X addresses.

### **On which chain need AVAX to be in order to stake?**

In order to stake, you need to transfer your AVAX to your P address.

### **Can I stake the AVAX that I purchased in the pre-sale?**

Yes, you can. Those are vested (locked) AVAX, and are directly available to your P address.You can delegate but you cannot move them to an X address.

### **Will staking rewards be on X-Chain or P-Chain?**

By default, staking rewards are allocated on the same P address used for the delegation.

### **When vested AVAX are unlocked, where are they?**

Vested (locked) tokens are in your P address, and when they unlock, they remain on your P address, but you can then freely transfer them to your X address.

### **If someone delegates to my node can I see their P address, amount and other information?**

Yes, you can do that by querying on your node. You will also be able to check it in the [Validators page](https://avascan.info/staking/validators) on Avascan soon.

### **Can I send AVAX from my P address to another P address?**

There’s no intention to add P to P transfers. The X-Chain is for exchanging assets so if you want to move funds between two P addresses you have to first move them to an X address: *P1 - X - P2*.

### **Are testnet validators different from mainnet validators?**

Yes, they’re different. Everest testnet validators are using a different version of the node. Each validator will then need to upgrade their node: this will change their NodeID. Be aware that if you don’t delegate on mainnet you won’t receive any reward!

### **If I delegate in testnet will I have to delegate in mainnet?**

Yes, you’ll need to add a new delegation to the mainnet validators. Their NodeID might be different from the one used in the Everest testnet.

### **What’s the difference between NodeID and validator?**

A validator is a node that belongs to the Default Subnet and validates the primary network. NodeID is its unique identifier.

### **If you delegate your AVAX you are just delegating for the validation of default chains?**

For the time being, when you delegate your AVAX, you are delegating a validator that belongs to the Default Subnet. The Default Subnet validates the primary network, which includes all the core chains, i.e. X-Chain, P-Chain and C-Chain.

Got another question? Get answers in the [Telegram community](https://t.me/AvascanExplorer) , our [Discord Server](https://discord.com/invite/CQJGs5B) or send a tweet to [@AvascanExplorer](https://t.me/AvascanExplorer).


# How to choose a validator

Choose the best validator to delegate according to your own profile (risk/reward ratio, liquidity, effort required)

{% hint style="warning" %}
S*eptember 21st update: this post has been updated to include the latest changes to Avalanche staking.*
{% endhint %}

### Introduction

AVAX delegation is **good business**, up to **12% per year**. But choosing a validator is a very delicate choice: you’re putting your future rewards in someone else’s hands. Despite appearances, Avalanche delegation is *not 100% trustless*: if your validator’s uptime drops <80% (for technical issues or - worse - deliberately because it’s an attacker) you’ll **lose** all your rewards, and there’s no option to unstake before the staking period ends.

Staking rewards depend on:

* **Duration**: the longer duration, the higher reward
* **Uptime**: must be *> 80%*

Choice depends on:

* **Risk** profile
* **Stake** amount
* **Effort** profile
* **Liquidity** profile

The goal of this post is to help you choose the best validator to delegate according to your own profile (risk/reward ratio, liquidity, effort required).

{% hint style="success" %}
**TL;DR**

Key takeaways:

* **Maximize safety**: Cautious saver (only option B)
* **Maximize risk/reward**: Lazy capitalist
* **Maximize ease**: Lazy capitalist, Lazy gambler
* **Maximize liquidity**: Obsessive trader (only option B).
  {% endhint %}

{% hint style="danger" %}
*Be suspicious of long term, anonymous, 0% fee validators with no track record and no accountability*
{% endhint %}

| Strategy            | Cautious saver | Lazy capitalist | Obsessive trader | Lazy gambler |
| ------------------- | -------------- | --------------- | ---------------- | ------------ |
| Sale option         | Option B       | All             | Option B         | All          |
| Validator trust     | High           | High            | Low              | Low          |
| Delegation fee      | High           | High            | Low              | 0%           |
| Delegation duration | 1 week         | 1 year          | 1 day            | 1 year       |
| Safety              | ★★★            | ★★              | ★★               | ★            |
| Reward              | ★★             | ★★★             | ★                | ★★★          |
| Risk/reward         | ★★             | ★★★             | ★                | ★            |
| Liquidity           | ★★             | ★               | ★★★              | ★            |
| Ease                | ★★             | ★★★             | ★                | ★★★          |

### Capacity

Validators' maximum weight is set at **3M AVAX** and a validator can’t collect delegations higher than *5 times its stake*. You therefore need to make sure your validator has enough capacity to accept your delegation.

### Duration

Your delegation strategy is mainly affected by your sale option and subsequent lockup period. **Duration** is one of the most important aspects of delegation. It affects *risk*, *reward*, *liquidity* and *effort*.

Higher staking period means **higher rewards** (up to a year). But since the tokens locked **cannot be unlocked** until the staking ends, you will need to think which period is the best for you. Bear in mind that it’s actually better to sync the staking period with the vesting period of the tokens you purchased in the token sale. Since the vesting period is 1 or 1.5 years, it may be better for you to stake for 1 year and then renew the stake with the new vested tokens.

Another important factor is how your amount staked relates with the tx fees you’re going to pay when renewing your delegation.

Delegation duration:

* **Short term**: less risk, more liquidity / more effort, less reward, more tx fees
* **Long term**: more risk, less liquidity / less effort, more reward, less tx fees

Depending on your sale allocation, there are different delegation durations that are optimal.

On the basis of your allocation:

* **Public sale A1**: you’re locked for **1 year**, you should delegate long term (e.g. 1 year) to optimize rewards;
* **Public sale A2**: you are locked for **1.5 years**, you should delegate long term (e.g. 1 year) to optimize rewards;
* **Public sale B**: you are fully liquid. You should choose between delegating long term (e.g. 1 year) to earn high rewards, or short term (e.g. 1 day) earning small rewards but preserving liquidity.

  **1. RISKS**

### Risks

#### Security risks

Despite appearances, Avalanche delegation is not 100% trustless: if your validator’s uptime drops <80% (for technical issues or - worse - deliberately because it’s an attacker) you’ll lose all of your rewards and you won’t be able to unlock your AVAX until delegation ends.

Imagine **Mallory** (fake name), a nasty Avalanche competitor, wants to damage Avalanche reputation. She buys 200,000 AVAX OTC, spawns dozens of low fee (0%, 0.1%, 1% etc) validators with long duration (10, 11, 12 months), collects lots of delegations from unwitting delegators. They happily proceed with the delegation, forget about it and plan to come back after a few months. When she collects 50M AVAX in delegations she turns her many nodes off, all at once. Since Avalanche has no slashing function, she won’t lose her 200,000 AVAX. Unfortunately all of her delegators will not only lose all rewards, but their AVAX will be locked until delegation ends. Avalanche will suffer a reputational loss, while delegators will lose money and liquidity.

Key questions:

* Is my delegator’s fee 0%?
* Can I double check the name and website of my validator?
* What’s their historical track record?
* Is my validator’s fee very low? If so, is it enough to pay for ongoing technical expenses and additional services?
* Is my validator’s staking duration higher than 6 months?

#### Technical risks

You need to understand how likely it is for your validator to go offline for technical faults, its contingency plans, and how large and skilled the team is.

* What’s the **specific hardware** setup of my validator?
* Is the hardware **powerful enough** to handle Avalanche peak traffic spikes (up to thousands of transactions per second)?
* **Where** is the node running and how **secure** is the location?
* Is the infrastructure **redundant**?
* What’s its **backup** policy?
* Is the node **protected** from DDoS?
* How is the node protecting its **private key**?
* What happens if a validator operator can’t, for any reason (illness, arrest, death, etc), **access and maintain** his node?
* Is the manager of the node able to maintain the validator, upgrade it and fix is quickly?

#### Other risks

* **Financial risk**:
  * What happens if your validator doesn’t have enough money to keep maintaining increasing hardware costs?
* **Regulatory risk**:
  * What jurisdiction is my node operator in?
  * Is the node physically under the same jurisdiction?
  * What happens if law enforcement, hosting provider, ISP chooses to stop your validator?

There are endless risks, as with any endeavor. Don’t fall for the illusion there are no risks.

### Safety

#### Fees

Do the math of your validator: Check the total delegated and the fee. How much will your validator **earn** per month? Do they offer **additional services or** one-on-one support?

If that’s not enough to maintain a professional service level, ask questions.

#### Trust

Be suspicious of new nodes (that have no track record), with unknown identity (no name, no website, etc.)

Questions:

* Am I sure this validator is **legit**?
* Are they **anonymous**?
* Is their website **trustworthy**?
* Do they have **experience** with staking?
* Are they rated or **audited**?
* Have they been **endorsed**?

#### Track record

Take a look at the **rewards’ track record**: it’s the most important aspect. Look at the last few months. That is not an indicator of future rewards, but a *good metric* nonetheless.

If the validator has a flawless track record for months or years, they are less likely to go offline unless they’re malicious. On the other hand, if they’re a malicious attacker, they will deliberately show a clean track record until they attack.

Key questions:

* How long has my validator been **active** on Avalanche?
* What’s its historical uptime for the last **12 months** (not its current one)?
* What’s its historical uptime for the last **6 months** (not its current one)?
* What’s its historical uptime for the last **3 months** (not its current one)?

The other important aspect is the **uptime track record**: look at the last few weeks / months. Not an indicator of the future, but a good metric here as well. And check if the validator is satisfying the **uptime requirements** of the network. On mainnet, there’s a threshold of 60% uptime. If a validator stays *below* 60%, they won’t get any staking rewards, and neither will you as its delegator.

### Additional rewards

Then you need to know more about **subnets**: how many subnets are they validating? Are they able and willing to add new subnets in the future?

Key questions:

* Will they share rewards from **new subnets** with me?
* Will they share **fork rewards** with me?
* Will my validator offer **additional rewards** beyond AVAX?
* Will my validator offer **additional services**?

### Governance

Avalanche will be governed **on-chain**, meaning that stakeholders will be able to take key decisions on how it should evolve. When you delegate your AVAX you also *delegate your voting power*. You validator will use its power to go to consensus about the uptime of other validators, to decide whether they will get the staking rewards - your decision will have an impact on the whole network!

Key questions:

* How will my validator **use** this power?
* Will I have a voice when key decisions happen, or will the validator choose what’s best for me?
* In the event of an **unexpected emergency** (imagine The DAO incident and subsequent decisions) will my voice be heard, or my validator’s?

### Support

You might need support to delegate, renew your delegation, secure your funds, etc: A validator with an **active support** is a great plus.

### More coming soon

We are hard at work on adding a tool on Avascan to help you choose which validator is best for you to delegate to. Stay tuned for more by following us on Twitter [@AvascanExplorer](https://twitter.com/AvascanExplorer), joining the [Telegram group](https://t.me/AvascanExplorer) and taking part in our [Discord dev community](https://discord.gg/AV6SMWM).


# Avascan validators

To help users, delegators, understand which Avascan validator to choose, we designed a table of comparison.

| Name                                                                                             | Stake   | Capacity  | Fee (SCAN Issued) | End                 | Why delegate?                                           |
| ------------------------------------------------------------------------------------------------ | ------- | --------- | ----------------- | ------------------- | ------------------------------------------------------- |
| ['Lazy' Snorlax](https://avascan.info/staking/validator/NodeID-V5R4XjWDtjs8Zi2g3TRNzngnGJiXm2ic) | 246,501 | 1,232,505 | 10%               | September 4th, 2021 | Avascan quality + get more SCAN tokens                  |
| [Ditto](https://avascan.info/staking/validator/NodeID-8ALyunjeYV85zBSrD2rjJdQ754z9jasvq)         | 90,000  | 311,853   | 7.5%              | September 4th, 2021 | Avascan quality + compromise for reward and SCAN tokens |

It’s very easy to find the Avascan validators: head to the [Validators page](https://avascan.info/staking/validators) and look for their names or, quicker, click on the names in this page to get to the specific Validator Details page. If you have a validator of your own and want it to be verified, apply for our [Validation Claim Program](https://docs.avascan.info/programs/validator-verification-program).

Happy delegations!


# Validator Claim

Instructions to claim your Validator on Avascan

Our Validator Claim Program is the way Validators can apply to become more recognizable for current and potential delegators, as well as users and developers, on the Avalanche network.

At launch, we support Alias and Icon visualization in the Validators list, as well as rich information in the Validator Details.

The information involved in the Verification are the following:

* **Alias**: the alias of the individual validator. If a single entity (company, individual) has more than one Validator, this is a great way of differentiating the set. For example, Avascan has two different Validators, so it uses different aliases for them, that coincide with the names used in our delegation campaigns on Twitter and Telegram: '[Lazy' Snorlax](https://avascan.info/staking/validator/NodeID-V5R4XjWDtjs8Zi2g3TRNzngnGJiXm2ic) and [Ditto](https://avascan.info/staking/validator/NodeID-8ALyunjeYV85zBSrD2rjJdQ754z9jasvq);
* **Icon**: An image that can represent the Alias, the Manager, or both. It's displayed in a square format. For example, for Avascan's Validators, the logo is Avascan's logo. We recommend an SVG or PNG format..
* **Manager**: the entity that manages the Validator. In our case, it's Avascan.

![](/files/qeYX92z6XiShxOvxkJly)

## What we don't accept in a claim

* Offensive or inappropriate alias/manager/icon
* Public people Names (including alias/manager/icon)
* Fake information (ex: Managed by Avascan/Avalabs if is not the case)

## How to claim?

* Go on <https://avascan.info/> and paste your validator's NodeID in the search bar

![](/files/GIzGXtjmhRc13Zy7f1dI)

* In "Beneficiary," you can see the address associated with your Node. This is the address you must use to sign the message

![](/files/TD1nEze86uXHZTaYroBx)

* Go to [https://core.app](https://core.app/) and access your wallet

*Make sure it's the wallet associated with the validator address*

* Go to Tools > Signing tools > Sign Message

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

* Select the address that matches the beneficiary address of your node
* Write your message using the following format:

NodeID-XXXXXXXXXXX "Alias" "Manager" < your website link > < your logo link >

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

* Click "Sign message" and approve
* Copy the generated signature
* Paste the memo and signature in the #avalanche-validator channel in our [Discord server](https://discord.gg/XxKz4gHy3J) and wait for our assistance

<figure><img src="/files/2r0QUgNfKwCupDwL9Va7" alt=""><figcaption></figcaption></figure>

## Removing/updating the Claim

If you want to remove or update a claim associated with one of your validators, you can do so by signing a new message including the NodeID and just one other field of your choice.

*Claims are processed daily, and all information will be updated within 24 hours on working days.*

{% hint style="info" %}
*If you have any question or need support reach out to us here:* <https://routescan.io/contactus>
{% endhint %}


# Asset Claim

How to add rich information to your asset on Avascan

{% hint style="info" %}
Got a question or need support? Ask in the [#✅programs in our Discord channel](https://discord.gg/n6A3YDX).
{% endhint %}

As per our announcement in the newsletter [**Explore #4**](https://blog.avascan.info/2020-10-16-explore-four.html), we introduce our **Asset Claim Program** (*ACP*, in short).

The ACP is supposed to be the way Minters can add rich information about the asset thay they created. Almost 180 assets have been deployed on X-Chain to date, and more will come, as the Avalanche network grows over time.

{% hint style="info" %}
For users: assets with details added via ACP are *not* verified. Avascan cannot verify the integrity of a specific asset other than **AVAX**, the main asset, and **SCAN**, the token deployed by Avascan itself. Avascan does not endorse any other asset. We will label public projects eventually.
{% endhint %}

The information involved in the Claim are the following:

* **AssetID**: the unique identifier of the asset on the Avalanche network;
* **Icon**: an image representing the coin/asset;
* **Minter:** the primary asset's manager or owner. It is the person that actually *mints* the coins.

For the time being, since Avascan is still under heavy development to properly support all types of assets, we will only claim assets that meet the following criteria:

* Single-address Minter;
* Fixed cap.

### How to apply for the Avascan Asset Details Program

Applying for the ACP requires the Minter to send two transactions:

#### **1. Details Tx**

* **Recipient address:** `X-avax1d2k252djnyeshjpgqggh6r8ntle966udf59s5g`;
* **Amount**: 1 AVAX;
* **Memo**: `AssetID MinterContact IconURL`

#### **2. Confirmation Tx**

* **Recipient address:** `X-avax1d2k252djnyeshjpgqggh6r8ntle966udf59s5g`;
* **Amount**: 1 unit of asset;
* **Memo**: `Verification_TxID`

{% hint style="warning" %}
We will only accept transactions sent from the `Minter` address. We cannot claim assets if you send the Details and/or Confirmation Tx from a different address.
{% endhint %}

The `Details_TxID` is the ID of the Details Tx. It is **not** the link, just the ID. For reference, this is a TxID (`HUhmMJZdx9AhEytBkdYTB124ptgGGeRMg7xaZyZc2ovgCxRrc`) and this is **its** Tx ID **link:** <https://avascan.info/blockchain/x/tx/HUhmMJZdx9AhEytBkdYTB124ptgGGeRMg7xaZyZc2ovgCxRrc>.

The `MinterContact` field is required for us as a double verification measure: it can be anything that can help us verify the Minter's identity:

* Telegram
* Twitter
* Discord
* Keybase
* GitHub

For example, to claim **SCAN**, we may send the Details Transaction of 1 AVAX with the following memo:

> 3ofDwYQKgBvsZQTBXJnqdvcns4aGikwSnGie2kc6xWJM7MAGb <https://t.me/AvascanExplorer> <https://example-cloud-storage.com/imageExample.svg>

As for the IconURL, you can use whatever service you want, both centralized (Dropbox, Google Drive, Box, iCloud) or decentralized (IPFS or similar). The only mandatory requirement is that the link MUST be public, and everyone needs to be able to download the file. Please upload the image in **SVG format** (preferred) or PNG, in squared format. We are currently not displaying Asset Icons, but are working to display them in the near future.

{% hint style="warning" %}
If the Icon URL is too long, please include a shortlink instead: you can use a service like Bitly or Rebrandly.
{% endhint %}

And then, for the Confirmation Transaction, we need to send **1 SCAN** with the following memo (example tx, not referred to SCAN's details):

> `HUhmMJZdx9AhEytBkdYTB124ptgGGeRMg7xaZyZc2ovgCxRrc`

We will process the applications within 24-48 hours.

{% hint style="info" %}
Got a question or need support? Ask in the [#✅programs channel in our Discord channel](https://discord.gg/n6A3YDX).
{% endhint %}


# Address Claim

Introducing **Meta Attributes for addresses.** This feature will let us map all the addresses available on Avalanche with additional details, including:

* **Alias**
* **Owner**
* **Unlock date** of the whole funds (if the address belongs to the genesis block);
* **Type**: can be an address related to an *exchange*, the *AEB bridge\**, a \*dapp, and much more!
* **symbol** for token contract addresses;
* **Icon**
* **Reputation**: this is a discretional tag, that Avascan staff will periodically update to reflect the status of the project related to the token address or address as it's perceived in the Avalanche community (and beyond). There are 4 tags:
  * *Unknown:* default for every address, it means that we don’t have enough information;
  * *Low:* meaning that there has been something suspicious about it;
  * *Medium:* there is a lot of chatter about it, but we don’t know if it’s a safe project or not;
  * *High:* we know the team, have high confidence and there’s good hype around it.

## How to claim ownership

Reading the name of your project and seeing your icon while browsing will surely enhance the trust of your investors.

![Your Project's name on Avascan's list of contracts and addresses](/files/-MjThgS0inliwzibRvDf)

![An example of a Project's address claimed with the Address Claim Program](/files/-MjThnW_PcaJGOiebuv9)

What do you need:

* A PNG or SVG logo&#x20;
* A list of your contracts addresses (via Docs link, Github link, just a written list, etc)

To claim ownership, write in our [Discord server](https://discord.com/invite/CQJGs5B) in the channel #addresses and provide us the list and/or the logo, we will immediately proceed to identity verification and then update the info.

![](/files/-MjTi5OjN8YnnZG9XCPF)

Your information will be updated shortly. Whenever a new address is added to your project, tell us and we'll provide the service.\
This helps us, helps you and also the community by preventing scam and augmenting trasparency.<br>


# The Blue Badge

How to get the Blue Badge and why it's so important

As Avalanche grows exponentially, we need a way to understand which tokens, contracts and addresses are relevant to the community and actually what they say they are.

There could be (and mostly are) many AVAX [tokens](/how-to-use-avascan/avalanche-tokens-list) on Avalanche, but only one is the genuine native token. In the same way, there are many duplicate tokens and it's hard for users to understand which one is the genuine, and how to avoid scams or contracts different from what they're expecting.

So, we're working with Ava Labs, as well as setting up our own team of forensic on-chain analysts, to get in contact with all the genuine projects on Avalanche, mapping their addresses, contracts and tokens, knowing the teams, to give them the **Blue Badge**.

The Blue Badge is **Avascan's way of telling users** that the Avascan staff is in **active contact** with the team developing the project, and that there's an ecosystem partnership between Avascan and the project's team. It's shown in the Avalanche Token List and in Search Results: tokens, addresses and contracts with the Blue Badge are **listed higher** in the list after a transition period of about two weeks, in which tokens are only sorted by market cap by default.

![The Avalanche Tokens List](/files/-MlPQCVnTUBtffQE8DJ7)

The Blue Badge is given to addresses, contracts and tokens of dapps that:

* Are **relevant** in the Avalanche ecosystem
* Are **known community projects** (e.g. meme coins)
* (Tokens) have **sufficient liquidity** on DEXs, such that it's easy to buy and sell a few thousand dollars worth without an excessive price movement (less than 2%)

Avascan will improve the requirements over time over feedback from the community.

In order to get the Blue Badge, the project's team needs to show **commitment** to Avascan and the Avalanche ecosystem with one of these activities:

* Sharing every address, token and contract address on-chain, as well as notify Avascan's staff of new ones deployed/created
* Working to compile and publish every contract's source code ([Verify Contract](https://avascan.info/blockchain/c/contract/verify))
* Set Avascan as the default explorer to show transactions and addresses on-chain or, if the project doesn't have a website or a way to show those data, linking the token contract on Avascan in the homepage or other relevant page.

To get started with the process, fill this form: <https://app.deform.cc/form/93452ae6-cc21-4464-8969-d26d86b84917/>


# How to verify smart contract

Submit your smart contract code for independent verification and publishing on Avascan

{% hint style="info" %}
If you'd like to verify contracts via our website, you may do so using the [**Verify Contract**](https://avascan.info/blockchain/c/contract/verify) page.
{% endhint %}

With the Etherscan Compatible Verify Contract API, verify smart contract on Avascan is now more easy than ever. There are few things you need to connect your favorite verify contract client with Etherscan compatibility:

1. Define the `networkId`: mainnet, testnet
2. Retrieve the `chainId` of the evm compatible blockchain. You can use the [**all blockchains page**](https://avascan.info/blockchains).
3. Compose the Etherscan Compatible API endpoint:  `https://api.avascan.info/v2/network/:networkId/evm/:chainId/etherscan`

The following endpoints are provided only as an example:

<table><thead><tr><th width="156">Blockchain</th><th>API Endpoint (https)</th></tr></thead><tbody><tr><td><p>C-Chain</p><p><em>mainnet</em></p></td><td><code>api.avascan.info/v2/network/mainnet/evm/43114/etherscan</code></td></tr><tr><td><p>Swimmer</p><p><em>mainnet</em></p></td><td><code>api.avascan.info/v2/network/mainnet/evm/73772/etherscan</code></td></tr><tr><td><p>C-Chain</p><p><em>testnet</em></p></td><td><code>api.avascan.info/v2/network/testnet/evm/43113/etherscan</code></td></tr><tr><td><p>WAGMI</p><p><em>testnet</em></p></td><td><code>api.avascan.info/v2/network/testnet/evm/11111/etherscan</code></td></tr></tbody></table>

### hardhat-etherscan

[**hardhat-etherscan**](https://hardhat.org/hardhat-runner/plugins/nomiclabs-hardhat-etherscan),  is an hardhat plugin, that simplify the smart contract verification process on Etherscan. With the Etherscan Compatible Verify Contract API, you can use this tool to verify your smart contract on Avascan as well.

Let's say you want to verify your smart contract on wagmi, this is an example of `hardhat.config.ts`:

```typescript
import { HardhatUserConfig } from "hardhat/config";
import "@nomicfoundation/hardhat-toolbox";
import "@nomiclabs/hardhat-etherscan";

const config: HardhatUserConfig = {
  etherscan: {
    apiKey: {
      wagmi: "avascan", // apiKey is not required, just set a placeholder
    },
    customChains: [
      {
        network: "wagmi",
        chainId: 11111,
        urls: {
          apiURL: "https://api.avascan.info/v2/network/testnet/evm/11111/etherscan",
          browserURL: "https://testnet.avascan.info/blockchain/wagmi"
        }
      }
    ]

  },
  networks: {
    wagmi: {
      url: 'https://subnets.avax.network/wagmi/wagmi-chain-testnet/rpc',
      accounts: [process.env.PRIVATE_KEY]
    },
  },
};

export default config;
```

#### Deploy

```
npx hardhat run scripts/deploy.ts --network wagmi
```

#### Verify

```
export PRIVATE_KEY=...
npx hardhat verify --network wagmi 0x...
```

If you need any support just ask in our [Discord server](https://discord.com/invite/CQJGs5B) or our [Telegram group](https://t.me/AvascanExplorer).


# How to setup your token marketcap

In this guide you can learn how to update your token market cap correctly. This information is useful both for you and the users.

**Important:** Please complete the form with the locked addresses to accurately display your token's market cap on Avascan

To calculate your marketcap we'll need the following:

* Your project name
* Your token name
* Your token addresses
* Team/Founder Addresses
* Reserve Addresses
* Burn Addresses
* Smart Contract Lock-up Addresses
* Vesting/Lock-up Addresses
* Staking Addresses
* Others Allocations Addresses

Once your are prepared just fill this form: <https://form.typeform.com/to/CSQDNMeq>

Don't hesitate to reach us for any further need


# Deploy and verify an ERC-20 token

### Step 1

First we’re going to create a new folder and install hardhat:

```bash
$ mkdir mock-token$ cd mock-token
$ npm init
$ npm install --save-dev hardhat
```

Now let’s bootstrap a hardhat project. Select the option "Create an empty hardhat.config.js":

```bash
$ npx hardhat 
```

Let’s also create a couple of folders for our files:

```
$ mkdir scripts contracts
```

Now install some dependencies to our project:

```bash
$ npm install --save-dev @nomiclabs/hardhat-ethers ethers @nomiclabs/hardhat-waffle ethereum-waffle chai
$ npm install --save-dev @nomiclabs/hardhat-etherscan
```

### &#x20;Step 2

Let’s now create a first Solidity contract at *contracts/Token.sol*:

```solidity
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.2;
 
import "@openzeppelin/contracts/token/ERC20/ERC20.sol";
 
contract MockToken is ERC20 {
    constructor() ERC20("Mock Token", "Mock") {
        _mint(msg.sender, 1000000 * 10**decimals());
    }
}
```

We need to install *openzeppelin* library to our file:

```bash
$ npm install @openzeppelin/contracts
```

Try to compile the contract with:

```bash
$ npx hardhat compile
```

### Step 3

We should prepare our *hardhat.config.js* file as:

```javascript
require("@nomiclabs/hardhat-etherscan");
require("@nomiclabs/hardhat-waffle");
 
const PRIVATE_KEY = "PRIVATEKEY";
 
module.exports = {
    solidity: "0.8.2",
    defaultNetwork: "fuji",
    networks: {
      mainnet: {
        url: `https://api.avax.network/ext/bc/C/rpc`,
        accounts: [PRIVATE_KEY]
      },
      fuji: {
        url: `https://api.avax-test.network/ext/bc/C/rpc`,
        accounts: [PRIVATE_KEY]
      }
    },
    etherscan: {
      apiKey: {
        fuji: "avascan" // apiKey is not required, just set a placeholder
      },
      customChains: [
        {
          network: "fuji",
          chainId: 43113,
          urls: {
            apiURL: "https://api.avascan.info/v2/network/testnet/evm/43113/etherscan",
            browserURL: "https://testnet.avascan.info/blockchain/c"
          }
        }
      ]
    },
};
```

### Step 4

Now let’s add the deploy script. To keep it simple we’ll simply reuse the deploy script from the Hardhat tutorial, so let’s create the file *scripts/deploy.js*:<br>

```javascript
const { ethers } = require("hardhat");
 
async function main() {
    const [deployer] = await ethers.getSigners();
 
    const Token = await ethers.getContractFactory("MockToken");
    const token = await Token.deploy();
    console.log("Contract address:", token.address);
}
 
main()
    .then(() => process.exit(0))
    .catch((error) => {
        console.error(error);
        process.exit(1);
    });
```

After wrote our script, we can call deploy file:

<pre class="language-bash"><code class="lang-bash"><strong>$ npx hardhat run scripts/deploy.js --network fuji
</strong><strong>$ npx hardhat verify --contract contracts/Token.sol:MockToken --network fuji &#x3C;contractaddress>
</strong></code></pre>

<figure><img src="https://lh6.googleusercontent.com/6AtMTs6deCbDhbM_nX65Q6VpEa3xxmcETKT3Rd8KsYumC7m83XrLLEuMLmd3BzF9zlZf3SxHpVs0Y76Sp5ozUhdSXG-157cHvkk3yAOUckRcbTOeep4qPsRy-t6beor5rleKfjyTb01wM2f4FKTLt8UrR8d0aZiHB2WESFAZagIhIu3z04DrHgf1w9qO5A" alt=""><figcaption></figcaption></figure>


# Documentation

{% hint style="info" %}
*If you want to increase the RPS/calls, you can purchase a plan at:*  [*https://routescan.io/documentation#api-plans*](https://routescan.io/documentation#api-plans)
{% endhint %}

API documentation is [here](https://routescan.io/documentation).

{% hint style="info" %}
*Do you need support? Reach out to us here*: <https://routescan.io/contactus>
{% endhint %}


# /api/v1 (deprecated)


# Supply (deprecated)

{% hint style="danger" %}
This endpoint has been deprecated.
{% endhint %}

## Get current AVAX Supply

<mark style="color:blue;">`GET`</mark> `https://avascan.info/api/v1/supply`

This endpoint gives more granular data about the AVAX supply based on a mix of real-time updates and editorial work of the Avascan team.

#### Query Parameters

| Name              | Type   | Description                                               |
| ----------------- | ------ | --------------------------------------------------------- |
| totalSupply       | number | total available AVAX supply (360MM + stakingRewards)      |
| circulatingSupply | number | genesisUnlock + stakingRewards                            |
| lastUpdate        | number | date of last update of the whole data set                 |
| stakingRewards    | number | total staking rewards minted                              |
| genesisUnlock     | number | unlocked AVAX at the time as per the AVAX Unlock Schedule |

{% tabs %}
{% tab title="200 Supply data correctely retrieved." %}

```
{
  "genesisUnlock": 65171868.28,
  "stakingRewards": 11765187,
  "lastUpdate": "2020-12-08T12:00:00.000Z",
  "circulatingSupply": 76937055.28,
  "totalSupply": 371765187
}
```

{% endtab %}
{% endtabs %}


# Statistics (deprecated)

Source staking statistics from the Primary Network

{% hint style="danger" %}
These endpoints have been deprecated.
{% endhint %}

## Get current AVAX Supply

<mark style="color:blue;">`GET`</mark> `https://avascan.info/api/v1/supply`

This endpoint gives more granular data about the AVAX supply based on a mix of real-time updates and editorial work of the Avascan team.

#### Query Parameters

| Name              | Type   | Description                                               |
| ----------------- | ------ | --------------------------------------------------------- |
| totalSupply       | number | total available AVAX supply (360MM + stakingRewards)      |
| circulatingSupply | number | genesisUnlock + stakingRewards                            |
| lastUpdate        | number | date of last update of the whole data set                 |
| stakingRewards    | number | total staking rewards minted                              |
| genesisUnlock     | number | unlocked AVAX at the time as per the AVAX Unlock Schedule |

{% tabs %}
{% tab title="200 Supply data correctely retrieved." %}

```
{
  "genesisUnlock": 65171868.28,
  "stakingRewards": 11765187,
  "lastUpdate": "2020-12-08T12:00:00.000Z",
  "circulatingSupply": 76937055.28,
  "totalSupply": 371765187
}
```

{% endtab %}
{% endtabs %}

## Global statistics

<mark style="color:blue;">`GET`</mark> `https://avascan.info/api/v1/home/statistics`

Get the updated statistics shown in the Avascan home page. Query data are selected when they’re equal to 1 (example: `blockchains=1`). Unspecified query data will lead to full output.

#### Query Parameters

| Name                         | Type   | Description                                                                                                                                  |
| ---------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
| blockchains                  | number | Total deployed blockchains on mainnet                                                                                                        |
| validators                   | number | Total validators validating the Primary Network                                                                                              |
| stakingRatio                 | number | Total staked AVAX out of total supply                                                                                                        |
| stakingRewards               | number | Current staking rewards' yield                                                                                                               |
| price                        | number | Current price from CoinGecko                                                                                                                 |
| marketcapByCirculatingSupply | number | Current market cap by circulating supply                                                                                                     |
| marketcapByTotalSupply       | number | Fully diluted market cap out of total supply                                                                                                 |
| circulatingSupply            | number | Current circulating supply: unlocked genesis + staking rewards - burned fees                                                                 |
| lastAvgTps24h                | number | Average transactions per second in last 24 hours                                                                                             |
| assetsAndTokens              | number | Aggregated count of assets on X-Chain and tokens on C-Chain. Does include NFTs on X-Chain, but not ERC-721 and ERC-1155 on C-Chain, for now. |
| burnedSinceLaunch            | number | Total AVAX burned in fees and burn addresses                                                                                                 |

{% tabs %}
{% tab title="200 " %}

```
{
    "blockchains": 10,
    "validators": 979,
    "stakingRatio": 55.78593411685608,
    "stakingRewards": 10.3812945775,
    "price": 14.74,
    "marketcapByCirculatingSupply": 2541443737.36665,
    "marketcapByTotalSupply": 5688491788.64565,
    "circulatingSupply": 172418164.00045115,
    "lastTransactions24h": 19387,
    "lastAvgTps24h": 0.22438657407407409,
    "assetsAndTokens": 4928,
    "burnedSinceLaunch": 115758.43176020411
}
```

{% endtab %}
{% endtabs %}

## Staking statistics

<mark style="color:blue;">`GET`</mark> `https://avascan.info/api/v1/statistics`

This endpoint allows you to source the same data present in Avascan's Staking Stats page.

#### Query Parameters

| Name                 | Type   | Description                                                        |
| -------------------- | ------ | ------------------------------------------------------------------ |
| totalValidator       | number | The count of validator validating                                  |
| totalDelegation      | number | The count of delegations in progress                               |
| totalStake           | number | Expressed in AVAX, it's totalValidationStake + totalDelegatedStake |
| totalValidationStake | number | Stake of 'totalValidator' validations                              |
| totalDelegatedStake  | number | Stake of 'totalDelegation' delegations                             |
| stakingRewards       | number | newly minted AVAX with staking                                     |
| stakingRatio         | number | Ratio of AVAX locked in stake vs. total supply                     |

{% tabs %}
{% tab title="200 Cake successfully retrieved." %}

```
{
    "totalValidator":865,
    "totalDelegation":5683,
    "totalStake":299584477.8758476,
    "totalValidationStake":209563806.4235764,
    "totalDelegatedStake":90020671.45227116,
    "stakingReward":9.607169410375027,
    "stakingRatio":83.21791052106877
}
```

{% endtab %}
{% endtabs %}


# Staking (deprecated)

Source validators data from the Primary Network

{% hint style="danger" %}
These endpoints have been deprecated.
{% endhint %}

## Get current AVAX Supply

<mark style="color:blue;">`GET`</mark> `https://avascan.info/api/v1/supply`

This endpoint gives more granular data about the AVAX supply based on a mix of real-time updates and editorial work of the Avascan team.

#### Query Parameters

| Name              | Type   | Description                                               |
| ----------------- | ------ | --------------------------------------------------------- |
| totalSupply       | number | total available AVAX supply (360MM + stakingRewards)      |
| circulatingSupply | number | genesisUnlock + stakingRewards                            |
| lastUpdate        | number | date of last update of the whole data set                 |
| stakingRewards    | number | total staking rewards minted                              |
| genesisUnlock     | number | unlocked AVAX at the time as per the AVAX Unlock Schedule |

{% tabs %}
{% tab title="200 Supply data correctely retrieved." %}

```
{
  "genesisUnlock": 65171868.28,
  "stakingRewards": 11765187,
  "lastUpdate": "2020-12-08T12:00:00.000Z",
  "circulatingSupply": 76937055.28,
  "totalSupply": 371765
```

{% endtab %}
{% endtabs %}

## Validators

<mark style="color:blue;">`GET`</mark> `https://avascan.info/api/v1/validators`

This API allows you to source data per each validator on the Primary Network.

#### Path Parameters

| Name    | Type   | Description                                                                                                                                                                |
| ------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| offset  | number | The starting point of the search                                                                                                                                           |
| limit   | number | Number of items to fetch                                                                                                                                                   |
| orderBy | object | Can be used with all numeric keys with 'desc' or 'asc' value: weight, startTime, endTime, delegatedWeight, delegations, capacity, delegationFee, maxYield, potentialReward |

{% tabs %}
{% tab title="200 Outputs all data shown in the Validator Details page, along with rich data about the beneficiaries." %}

```
{
    "count":1004,
    "results":
        [
            {
            "id":"NodeID-3DwhPYMEQABuocceWDAZEpi8GMcLyvTYy",
            "weight":3000000,
            "startTime":"2020-09-22T09:24:17.000Z",
            "endTime":"2021-09-22T09:24:17.000Z",
            "status":"active",
            "delegatedWeights":1313691.75,
            "delegations":34,
            "capacity":0,
            "delegationFee":0.0999,
            "maxYield":0.0999,
            "potentialReward":197357.255653572,
            "beneficiary":
                    {
                    "locktime":"0",
                    "threshold":"1",
                    "addresses":
                        [ "P-avax1p9w2g4nds47d83sa7vqtm2g3yr28mp7f6pd7tt"]
                    }
            }
        ]    
}
        
```

{% endtab %}
{% endtabs %}

## Delegations

<mark style="color:blue;">`GET`</mark> `https://avascan.info/api/v1/delegations`

This API allows you to source data about all the delegations in progress. It **does not** provide historical delegations. No parameter is needed.

{% tabs %}
{% tab title="200 " %}

```
{
    "items":
        [
            {
                "beneficiary":
                    {
                        "locktime":"0",
                        "threshold":"1",
                        "addresses":
                        ["P-avax1ef0yud6tj9xt2t7gt8gnkzf0kksw4wfgpwm78v"]
                    },
                "txid":"zJUu4d87L8fakqx1ayPUNcvuxk2bKiKLUnyQjqrTvCwKdtMti",
                "weight":2324960,
                "nodeID":"NodeID-77sRzBARyvwQk9g4d2CZaucRQeRA7SJuh",
                "potentialReward":34302.056718573,
                "startTime":"2021-07-06T13:48:44.000Z",
                "endTime":"2021-09-04T23:00:19.000Z"
            },
        ...
        ]
}            
```

{% endtab %}
{% endtabs %}


# Burned fees (deprecated)

{% hint style="danger" %}
These endpoints have been deprecated.
{% endhint %}

## Get current AVAX Supply

<mark style="color:blue;">`GET`</mark> `https://avascan.info/api/v1/supply`

This endpoint gives more granular data about the AVAX supply based on a mix of real-time updates and editorial work of the Avascan team.

#### Query Parameters

| Name              | Type   | Description                                               |
| ----------------- | ------ | --------------------------------------------------------- |
| totalSupply       | number | total available AVAX supply (360MM + stakingRewards)      |
| circulatingSupply | number | genesisUnlock + stakingRewards                            |
| lastUpdate        | number | date of last update of the whole data set                 |
| stakingRewards    | number | total staking rewards minted                              |
| genesisUnlock     | number | unlocked AVAX at the time as per the AVAX Unlock Schedule |

{% tabs %}
{% tab title="200 Supply data correctely retrieved." %}

```
{
  "genesisUnlock": 65171868.28,
  "stakingRewards": 11765187,
  "lastUpdate": "2020-12-08T12:00:00.000Z",
  "circulatingSupply": 76937055.28,
  "totalSupply": 371765187
}
```

{% endtab %}
{% endtabs %}

## Get burned fees

<mark style="color:blue;">`GET`</mark> `https://avascan.info/api/v1/burned-fees`

This endpoint provides aggregated data about burned fees.\
\
No *Request* parameter is required. Look at the *Response* tab for information and examples about the expected output.\
\
*Note: data provided are only related to X-Chain and C-Chain for now. They will be updated with data from P-Chain once Norge 2.0 is out.*

{% tabs %}
{% tab title="200 The response provides the total burned fees since launch on X-Chain (X), on C-Chain (C) and on the two chains together (XC)." %}

```
{
    "X": 1943.605,
    "C": 53165.52827869984,
    "XC": 55109.13327869985
}
```

{% endtab %}
{% endtabs %}


# GraphQL (deprecated)

Explore the Avalanche platform easily using Avascan's API endpoints. Docs will be updated weekly as we approach Avalanche mainnet. API is still under development.

## API version 0.3

{% hint style="danger" %}
GraphQL APIs are deprecated for now. We will provide new APIs when our new Norge v2 indexer is complete.
{% endhint %}

## Avascan API

Avascan is the most complete, fast and privacy-focused explorer for the Avalanche network. With Avascan API developers can build apps and tools. You can start queries by accessing the [GraphQL Avascan API Playground](https://graphql.avascan.info).

{% hint style="warning" %}
Note: currently queries only show results for X-Chain. P-Chain and C-Chain are not indexed yet.
{% endhint %}

## Blockchains

Avalanche is the 'internet of blockchains', and as such, you can browse and extract info about a given blockchain. Currently, there are only three permissionless blockchains nicknamed *P-Chain*, *X-Chain* and *C-Chain*. There are also permissioned blockchains, and both permissionless and permissioned will likely increase in number when the mainnet is launched. You can browse blockchains with a simple query: you will get the number of blockchains in the Avalanche network.

```bash
query {
  blockchains {
    count
  }
}
```

You can also get more specific information about a single blockchain.

{% tabs %}
{% tab title="Query 1" %}

```bash
query {
  blockchains(limit: 5, offset: 0) {
    count
    results {
      id
      name
      subnet
      vm
```

{% endtab %}

{% tab title="Query 2" %}

```
query {
  blockchains(id: "2oYMBNV4eNHyqk2fjjV5nVQLDbtmNJzq5s3qs3Lo6ftnC6FByM") {
    count
    results {
      id
      name
      subnet
      vmID
    }
  }
}
```

{% endtab %}
{% endtabs %}

## Transactions

If you want more info on a specific blockchain, query its transactions. Do it by passing the `assetID` and you can order it by any attribute, `desc` or `asc`. You need to specify the attributes you want to get in the result response, as shown below:

```
query {
  transactions(
    assetID: "3ofDwYQKgBvsZQTBXJnqdvcns4aGikwSnGie2kc6xWJM7MAGb"
    limit: 10
    offset: 0
    orderBy: { acceptedAt: "desc" }
  ) {
    count
    results {
      ... on XBaseTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
      }
      ... on XCreateAssetTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
      }
      ... on XExportTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
      }
      ... on XImportTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
      }
    }
  }
}
```

{% hint style="warning" %}
Note: ordering by certain variables may not be available yet.
{% endhint %}

You can also filter the transactions to obtain the ones that are specific to a certain asset filtering by `assetID`:

```bash
query {
  transactions(
    assetID: "3ofDwYQKgBvsZQTBXJnqdvcns4aGikwSnGie2kc6xWJM7MAGb"
    limit: 10
    offset: 0
    orderBy: { acceptedAt: "desc" }
  ) {
    count
    results {
      ... on XBaseTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
      }
      ... on XCreateAssetTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
      }
      ... on XExportTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
      }
      ... on XImportTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
      }
    }
  }
}
```

Or you can filter by `address`:

```bash
query {
  transactions(
    address: "X-avax149ssfat0569urv3xgppnz08ffrch5yjkzfs3xz"
    limit: 10
    offset: 0
    orderBy: { acceptedAt: "desc" }
  ) {
    count
    results {
      ... on XBaseTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
      }
      ... on XCreateAssetTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
      }
      ... on XExportTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
      }
      ... on XImportTransaction {
        inputs {
          output {
            id
            transactionID
            outputIndex
            assetID
            outputType
            amount
            locktime
            threshold
            addresses
            redeemingTransactionID
            type
          }
          credentials {
            address
            publicKey
            signature
          }
        }
        outputs {
          id
          transactionID
          outputIndex
          assetID
          outputType
          amount
          locktime
          threshold
          addresses
          redeemingTransactionID
          type
        }
        id
        chainID
        type
        acceptedAt
      }
    }
  }
}
```

## Address outputs

Get a series of UTXO-related info for a specific address by including a `redeemingTransactionID` that shows if the output related to that address has already been spent.

```bash
query {
  outputs: outputs(address: "X-avax149ssfat0569urv3xgppnz08ffrch5yjkzfs3xz") {
    count
    results {
      ... on XOutput {
        id
        transactionID
        outputIndex
        assetID
        outputType
        amount
        locktime
        threshold
        addresses
        redeemingTransactionID
        type
      }
    }
  }
}
```

## Get the list of validators

Get a complete list of validators, both *active* and *pending*. You can order the result by `startTime`, `endTime`, `weight`, `address`, `subnet` or `id`.

```bash
query {
  validators(
    status: "active"
    limit: 10
    offset: 0
    orderBy: { endTime: "asc" }
  ) {
    count
    results {
      id
      weight
      beneficiary {
        addresses
      }
      startTime
      endTime
      subnet
      status
      delegatedWeights
      delegations
      subnets {
        weight
        startTime
        endTime
        subnet
        status
        delegatedWeights
        delegations
      }
    }
  }
}
```

## Get the list of delegators

```bash
query {
  transactions(
    chainID: "p-chain"
    limit: 10
    type: "P_ADD_DEFAULT_SUBNET_DELEGATOR"
    offset: 0
    orderBy: { acceptedAt: "desc" }
  ) {
    count
    results {
      ... on PAddDefaultSubnetDelegator {
        id
        chainID
        type
        acceptedAt
        weight
        from
        nodeID
        beneficiary {
          addresses
        }
        startTime
        endTime
      }
    }
  }
}
```

The Avascan API Platform is still under heavy development, and many more endpoints will become available soon.

[Join our Discord](https://discord.gg/CQJGs5B) chat to stay updated and connect with the team, ask for new features or give feedback.


# /api/v2


# Supply

## Get current AVAX Supply

<mark style="color:blue;">`GET`</mark> [`https://api.routescan.io/v2/network/mainnet/evm/43114/supply`](https://api.routescan.io/v2/network/mainnet/evm/43114/supply)

This endpoint gives more granular data about AVAX supply based on a near real-time updates.

#### Query Parameters

{% hint style="info" %}
Please remember, that query parameters are case sensitive.
{% endhint %}

<table><thead><tr><th>Name</th><th>Type</th><th>Description</th><th data-type="content-ref">Link</th></tr></thead><tbody><tr><td>totalSupply</td><td>number</td><td>total available AVAX supply (360MM + stakingRewards)</td><td><a href="https://api.routescan.io/v2/network/mainnet/evm/43114/supply?q=totalSupply">https://api.routescan.io/v2/network/mainnet/evm/43114/supply?q=totalSupply</a></td></tr><tr><td>circulatingSupply</td><td>number</td><td>genesisUnlock + stakingRewards</td><td><a href="https://api.routescan.io/v2/network/mainnet/evm/43114/supply?q=circulatingSupply">https://api.routescan.io/v2/network/mainnet/evm/43114/supply?q=circulatingSupply</a></td></tr></tbody></table>

{% tabs %}
{% tab title="200 Supply data correctely retrieved." %}

```
{
  "totalSupply": 459612306.108156,
  "circulatingSupply": 426276406.108156
}
```

{% endtab %}
{% endtabs %}