Neon’s Blockscout explorer is the main tool for viewing everything happening on Neon EVM - from transactions and account activity to smart contracts and tokens.

For Neon, Blockscout is unique since it contains links to Solana-side transactions as well as all the details on the EVM-side transactions.

What you can do with Neon’s Blockscout:

• Track wallets, tokens, and transactions in real time
• Debug smart contracts using logs and raw traces
• Access verified contract data and token prices
• Use the API to build tools or run analysis

Neon EVM is a Solana network extension that brings Ethereum compatibility to Solana’s high-speed infrastructure. This means developers can use familiar Ethereum tools and smart contracts, while transactions also include related Solana-side activity.

Thanks to this setup, each transaction in Blockscout shows both the Ethereum-style execution and links to its corresponding actions on Solana, giving you a complete picture of what’s happening under the hood.

This guide will walk you through how to navigate the Blockscout explorer, understand Neon EVM’s on-chain data, and make the most of its features.

If you're trying to:

• Look up a wallet address
• Check the status of a transaction
• Explore a smart contract

… then just paste the address or hash into the search bar at the top of the page https://neon.blockscout.com/.

The explorer will direct you to the relevant page with detailed information. You can also search by ENS - a human-readable registered name for an address.

Use the Network selector at the top right of the page to choose between:

• Devnet – For development and testing. You’ll see transactions related to test tokens and dApp experiments as you build.
• Mainnet – For real-world token transfers, contract interactions, and production-ready deployments.

Always double-check your selected network to make sure you’re exploring the right environment for your goal.

Scroll down the landing page to see latest blocks and transactions updating in near real-time, thanks to Neon’s subsecond block times averaging 0.4 seconds.

You can also go to REST API endpoint in the API section of the sidebar, where you can call the API endpoints directly from the Blockscout UI or from your own project to fetch the latest blocks and transactions.

Filtering by these entities is available from the sidebar: in particular, Blockchain section with sub-sections for Transactions, Internal transactions (none for Neon), Blocks, Top accounts and Verified Contracts allows you to access the filtered data for these categories and see their details.For example, Transactions view will give you txs specifying their type (e.g. Token transfer), method (e.g. swapExactETHForTokens), From/To addresses, etc.

If you need to see block updates in real-time, then Blocks view is what you need. Thanks to Neon’s fast block times (averaging around 0.4 seconds), this list updates near real-time, showing new blocks almost immediately after they are finalized.

For each block, you can see the total gas used - the sum of gas consumed by all transactions within that block. This metric is crucial for understanding network load and congestion at any given moment. Gas limit shows the maximum gas allowed in the block, which affects how many transactions can fit.

Traders and users can watch transaction throughput and gas usage to decide the best times to send transactions, while developers and validators can monitor block production performance and verify that the network is operating smoothly.

‍

To find a list of tokens used on Neon, token transfers, and a DEX prices for those tokens (available only on mainnet), you can go to Tokens section of the sidebar.

Getting a list of tokens on Neon EVM is also available both from the Blockscout UI in the Tokens section and in the REST API endpoints that you can call from your project. The data you can get in the Blockscout UI for tokens includes their price, on-chain market cap, and the number of holders.

The REST API, however, gives you a more extensive view on the token details, including the total supply, exchange rate, number of holders, icon URL, and so on.

Another handy tool in this section is the DEX tracker which aggregates token prices from various liquidity pools for Neon EVM token pairs. Instead of checking multiple DEX platforms separately, you get a unified dashboard showing token prices and liquidity data all in one place with a clear visibility of market depth and stability.

The DEX tracker gets its data grom Gecko, so you can also view the liquidity pool updates in Gecko termnial by clicking on its icon.

To read and interpret dynamic data for Neon EVM transactions, blocks, accounts, and more, you should use the Charts and Stats section available on the sidebar. This section provides a comprehensive, real-time overview of key blockchain metrics through interactive charts and detailed statistics, helping you understand network activity and performance trends.

• You can customize the time range for all charts to analyze trends over days, weeks, or months.
• The charts are interactive, so you can hover or click on chart elements to get detailed metric descriptions and exact values.
• You can download charts as PNG or CSV files for offline analysis or share them directly, or you can open them in full screen mode.

Then there’s an API section that allows to view connectable RPC endpoints, see the list of available REST API calls and schemas, and a GraphQL playground to get Neon on-chain data from within the blockscout UI.

Developers can use this section to quickly prototype and build dApps, analytics tools, or blockchain explorers using Neon’s on-chain data, and users can get a more comprehensive understanding of various parameters behind Neon transactions.

REST API is a powerful tool to get all kinds of data about Neon EVM.

Instead of manually parsing blockchain data, you can use these REST endpoints to programmatically fetch specific data sets in a standardized format (usually JSON).

For example, a list of addresses that hold NEON tokens can be fetched by calling the Get/addresses endpoint.

This particular enpoint is useful if you want to:

• Analyze top NEON holders
• Track verified contracts or known entities
• Pull address-level data for dashboards, explorers, or analytics tools

To get a list of verified smart contracts, you can call the Get/smart-contracts endpoint.

With this endpoint, you can track specific contract types (e.g. aggregators, routers, or bridges), analyze compiler and optimization usage, and display all this data in your dApp’s frontend.

The Other section contains options to verify and publish a cotnract, track Neon gas fees, and submit requests to publicly label or tag specific wallet addresses or smart contracts on Neon EVM.

To verify a contract, all you need to do after deploying it is add its address and compiler type in the respective fields here on Blockscout. And then you can also go to Submit public tag section to add a human-readable name to your contract and specify what type of contract it is - a protocol, classifier, general label, etc.

The Gas tracker sub-section in Other category of the sidebar shows the dynamic changes in gas fee prices on Neon EVM. You can view both current updates of network utilization (percentage of gas used compared to the gas limit), and gas price history. Tracking gas usage helps you estimate transaction costs and network demand trends.

Plus, if you click on Charts and stats right above the gas price flow chart, you’ll open the numbers for average gas price, total gas usage, and avg. amount of gas used per block.

Let’s walk through a real example: a user swapping WNEON for bridged USDC using IceCreamSwap.

Paste the transaction hash into the search bar to open the Transaction Details page.

1.1 The first thing we see under Details is the Transaction hash.

The hash field is more than just a hash at Neon because it also includes a link to a corresponding Solana tx. This transaction swaps wrapped Neon tokens to USDC through an IceCreamSwap Router.

Clicking on the Solana tx link leads you to Solscan.io the Solana-side transactions that interacted with Neon EVM to make this swap.Solana-side txs will contain account creation for the SPL tokens, minting and transferring the tokens from one PDA to ATA, and finally to the user’s account.

1.2 Status and method show if the tx was successful, still pending, or failed.

1.3 Block field shows the block number and the number of block confirmations.

1.4 Timestamp shows the date and time of of transaction inclusion, plus the length of time for confirmation.

1.5 From field shows the address of a user or contract that originated the transaction.

1.6 Interacted with contract shows the address of a user or contract that received the transaction.

1.7 Token transferred shows a list of tokens transferred within this tx.

1.8 Tokens minted shows a list of tokens that were minted in this tx.

1.9 Value shows the value in the native token (NEON).

1.10 Transaction fee for the total tx (in NEON).

1.11 Gas price shows the price per unit pf gas specified by the sender, displayed in both NEON and Gwei.

1.12 Gas usage and limit by txn shows how much gas your transaction actually used versus the maximum amount of gas you allowed it to use:

• 19,398 - This is the actual gas used by the transaction. It represents the amount of computational work required to execute your transaction.
• 200,703 - This is the gas limit you set for the transaction. It’s the maximum amount of gas you were willing to allow the transaction to consume.
• 9.67% - This is the percentage of the gas limit that was actually used. In this case, the transaction only used 9.67% of the maximum gas you allowed.

Go to the Token Transfers tab to see which tokens moved and between which addresses.

In case of our sample swap transaction:

• The transaction is a token swap where the user swaps nearly 0.96 WNEON for 0.0913 bridged USDC using IceCreamSwap on Neon.
• The WNEON is sent to the router, which then passes it to the swap pair.
• The pair returns the equivalent value in bridged USDC to the user.

There are no internal txns for Neon transactions since there’re no internal transfers between contracts on Ethereum happening on Neon EVM.

However, you can say that internal transactions are the ones that we saw attached to the transaction hash field in the Transaction window - these are the corresponding ‘internal’ transactions happening between accounts on Solana.

In the Logs tab, you can see what events were emitted during the transaction. These aren’t actual transfers but contract-emitted messages showing what the contract claims it did.

Example:

• A Deposit event from the WNEON contract showing how much was deposited and to whom.
• A Transfer event indicating movement of tokens.

These are useful for developers debugging or building frontend apps.

The State tab gives you a before-and-after snapshot of all the token balances affected by the transaction. In our case:

• How much WNEON left the user’s wallet;
• How much USDC they received;
• What changed in the liquidity pool;
• Fees paid to the miner (operator).

If you want to see what actually happened inside the smart contracts - not just events, but all calls and sub-calls, go to the Raw Trace tab.

This shows:

• Each contract function called;
• Value transferred;
• Gas used;
• Return data.

It’s a developer-facing view similar to a step-by-step debugger.

Blockscout makes transaction data on Neon EVM transparent, searchable, and actionable. Whether you're tracking token flows, verifying contracts, labelling addresses, or pulling on-chain data into your dApp via the API - Blockscout gives you the tools to do it.

What makes it unique on Neon is the ability to trace every transaction not just on the EVM level, but also see what happened on the Solana side via links to Solscan in each transaction details.

Learn more about verifying contracts on Blockscout in Neon’s docs and join our Discord to ask questions about fetching Neon’s data, adding Blockscout as a default explorer to your project, or even about the weather. 🌤️

See you on Discord!

‍