NeonScan is currently live on Devnet. The tool gives users a standard block explorer interface to search the Neon EVM for information such as block data, transactions, and addresses.
In this article, we’ll go into more detail about the NeonScan integration with the Neon EVM. Keep reading to learn about the features and benefits of NeonScan, how NeonScan queries for data, developer and end-user experience, and what’s in store for the future of NeonScan.
The Features and Benefits of NeonScan
NeonScan is an indexer and block explorer similar to Etherscan and Solscan. The tool was created in partnership with the Solscan team, which spearheaded the development of the NeonScan UI and backend functionality.
NeonScan gives developers and users in the Neon ecosystem access to easily digestible public data related to transactions, smart contracts, and accounts. This type of information allows users and developers on the Neon EVM to:
- Understand whether a transaction was successful or functioned as intended
- Understand how transactions interact with various accounts and programs (which is great for determining whether a dApp is safe/reliable).
- Debug smart contract code.
- Review token transfers and account balances.
- Review transaction data and metadata.
How NeonScan Queries For Data
Operations on the Neon EVM all have underlying impacts on the Solana blockchain. As such, all Neon transactions are made up of one or more Solana transactions. (Ethereum-like transactions may exceed the size limit of a single Solana transaction; as a result, multiple Solana transactions are needed to carry out the execution iteratively). Due to this complexity, NeonScan’s data queries source information from two locations: the Neon EVM and the Solana network.
The tool queries the Neon EVM for information using Ethereum-like APIs implemented by the Neon Labs team. The APIs provide developers with a simple and efficient method to gather data on Neon transactions and the associated Solana transactions. For pulling data from the Solana network, NeonScan leverages dedicated RPC endpoints.
Once data has been gathered, NeonScan stores the information on a database maintained by the NeonScan team. All the queried information is available on the NeonScan page and via a user-friendly API.
NeonScan Developer and End User Experience
After a user has executed an operation on the Neon EVM, they can navigate to neonscan.org (shown below) to look up their transaction, either by account or transaction ID. Users can view the Neon transaction details and the details of the underlying Solana transaction(s) that make up the Neon transaction. In addition to transaction details, users can view arbitrary account information, block details, and token information.
The NeonScan landing page offers a familiar UI/UX for Ethereum and Solana. The top half of the page features at-a-glance information such as NEON price and market cap (info not yet available as the NEON token is currently not present in any markets), network info (transactions metrics and last block), and key Neon EVM stats. The bottom portion provides a feed of the latest transactions and blocks.
NeonScan Release and Future Development
NeonScan is in active development on Devnet and will be launched on Mainnet at the same time as the Neon EVM. Currently, the team is iterating on the tool to address identified issues and to continue making enhancements to align with the pace of Neon EVM development.
Pending NeonScan developments include:
- Displaying live NEON price and market cap
- Displaying at-a-glance TPS
- Displaying a list of verified contracts and contract details
- Displaying assets stored within a contract
- Displaying transactions associated with a contract
- Adding public tags for notable wallets (exchanges, pools, scammers)
Neon Labs is Here to Help
If this article leaves you with further questions about the NeonScan integration, contact our team via Discord. We’ll be more than happy to elaborate on any details regarding NeonScan and explain how it can help both end users and developers better understand the underlying operations behind Neon transactions.
