Avascan blog


Nov 20th, 2020

Explore is partnering with the This Week in Avalanche to get news about the Avalanche ecosystem.


News about the Trustless Lending Program

Since we started talking about the TLP, we learned so much about how to help big holders manage their money safely and securely. After launchin Lazy Snorlax and Ditto validators at launch, we launched Abra that has just ended its validation period. We are now able to take this Program one step further, but we can’t announce everything yet, we still need to iron out some details.

In the meantime, if you have more than 20,000 AVAX and want to start a partnership with us to truly secure and anonymize your AVAX, contacts us in our Telegram community, so we can add you to the pipeline and let you know when the Program is ready.

This week in Avalanche

  • AvalancheGo v1.0.5 released - includes performance improvements and some quality of life improvements. N.B. the next release v1.0.6 will contain breaking changes, validators will be required to upgrade their nodes;
  • Ava Labs teased plans to launch AVAXWAP a Uniswap implementation on the C-Chain.

Read more on This Week in Avalanche, Nov 19, 2020

This week in Avascan

We now mapped 170 validators both with the Validator Claim Program and our forensics work on-chain!

Want to claim your validator? Click here.

What’s new on Avascan

We told you we had something in the works and now we have it: yesterday we deployed C-Chain exploring features to Avascan!

Acessing it is simple: click on the C-Chain button in the upper menu and you will see the Transactions on C-Chain page, listing transactions with their hash, block age, amount and type. There are different types of transactions on C-Chain:

  • ERC20 TRANSFER: involves the transfer of one or more ERC20 tokens;
  • CONTRACT CALL: represents an interaction with a contract;
  • IMPORT from X-Chain;
  • EXPORT to X-Chain;
  • ERC20 MINT: involves the minting of an ERC20 token. This is often coupled with an ERC20 TRANSFER;

These data are also available in the Transaction details page, along with rich information such as:

  • Nonce output in the transaction;
  • Richer representation of gas used out of total gas estimated to be used;
  • List of actions included in the transaction;
    And for developers:
    • Input data;
    • Execution tree (with a basic syntax highlight in JSON);
    • Logs.

Since C-Chain is EVM-based, the chain follows an account model (different from the UTXO model used in X-Chain) and transactions are aggregated in blocks, rather than processed in vertices (as it happens on X-Chain). This means that we can also map blocks, that you can see in the BLOCKS tab. For each block, we display its:

  • Height;
  • Age as timestamped on the chain (while on X-Chain we only display our time of acceptation of a transaction);
  • Number of transactions included in that block;
  • Gas used to process that block;
  • AVAX burned;
  • Size.

These data are also available in the Block details page, along with its complete hash and the list of the transactions involved in that block.

And finally, Tokens. A token on C-Chain is displayed in pretty much the same way as an Asset on X-Chain, with the inclusion of the number of holders of that token.

We hope you like it, but since is the first deployment, let us know what you think and how to improve it!

Known issues

  • We are aware of an issue that can cause temporary downtime in the whole website and, specifically, in some Asset Details pages. We are working on a solution that’s part of a major architectural overhaul of the website, that will likely be deployed by Christmas holiday.

Explore the Road

  • We are in the last phase of development for the new indexer. Its’ blazing fast and shows even more data about transactions. Can’t wait to tell you more about it when we launch it early next month.

We want to hear your feedback: head to our Changemap page to request new features or report bugs, and start a conversation in the #feedback channel in our Discord server or in the Telegram community.

See you next week, and thank you for reading!