VLXA block explorer is a search engine for a blockchain. Velas has two: one for the EVM side, one for the native side. The tracker above supports EVM transaction hashes (66 characters starting with 0x), EVM addresses (42 characters) and native transaction signatures (long base58 strings). It calls public endpoints directly from your browser; if they are unavailable, it says so rather than inventing a result.
EVM explorer
The EVM explorer shows blocks, transactions, tokens and contracts in the format Ethereum users know. Use it for ERC-style tokens and DeFi interactions.
Native explorer
The native explorer covers the Solana-derived side: slots, validators, stake accounts and native transactions. Fees there are expressed in lamports, the smallest unit.
Reading a transaction
| Status | Success or failed. A failed transaction still pays a fee. |
|---|---|
| Block or slot | Where it was recorded, useful for ordering. |
| From / To | Sender and receiver. A contract address on the To side means a contract call. |
| Value and fee | Amount moved and cost paid in VLX. |
Troubleshooting
- Pending for long: the hash may be wrong, or the transaction never reached the network.
- Not found: check you are on the right side (EVM versus native).
- Exchange withdrawal missing: confirm the network you chose matches the explorer.
For concepts, see how Velas works, and for fees, fees and speed.
What a block explorer shows and why it matters
A block explorer is the only neutral way to confirm what happened to a transaction. Exchange and wallet screens can lag, fail to refresh or show a status that does not match the chain. The explorer reads the chain directly. This is useful in three common situations: you sent funds and want to be sure they arrived, you are waiting for an exchange deposit and want to see whether it is confirmed, or you want to check a token or contract before interacting. Anything you can see on the explorer is public, including your own address balance and history, which is worth remembering if you want privacy.
Addresses and what they tell you
Looking up an address shows its balance, its token holdings and its history of transactions. On the EVM side you can also see whether an address is a contract, and often the verified source code. A newly created address with a single incoming transfer is typical of a fresh wallet; an address with thousands of outgoing small transfers might be a bot or an exchange hot wallet. Use that to sanity-check anyone asking you to send funds: if the address was created yesterday and has received many deposits from different people, be suspicious.
Contract pages
For a token or application, open its contract page on the EVM explorer and look at the creation date, the creator, the number of transactions and whether the code is verified. Verified source code means the explorer compared the published code with the deployed bytecode. It is not a safety guarantee, but unverified code on a contract that asks for your approval is a real warning sign. Read the events log of a recent transaction to see exactly what tokens moved.
Native explorer extras
The native explorer is where you check validators, stake accounts and recent blocks. If you stake, you can find your stake account and see its state: activating, active or deactivating. It also helps you compare validators by looking at their stake and vote activity. See the validators guide and staking guide for how to use that information.
Understanding statuses and confirmations
A transaction can be pending, included and successful, or included and failed. A failed transaction still paid a fee because validators did the work, a common surprise. A single confirmation is usually enough for a small transfer, but a platform that credits deposits may wait for more. When you troubleshoot, the order is: confirm the hash is correct, confirm you are on the correct explorer side, confirm the status, and then look at the destination address. If the destination is different from what you intended, no one can reverse it.
Using the tracker on this page
The tracker queries the public RPC endpoint at https://evmexplorer.velas.com/rpc from your browser, so it relies on that service being available. If it fails, use the explorers directly. Never enter a recovery phrase or private key in any tracker, including ours; a legitimate explorer never asks for one. For fee questions, see fees and speed.
Habits that make explorer lookups reliable
The most common mistake is pasting a hash or address into the wrong explorer. A 0x hash belongs to the EVM side, while a long base58 signature belongs to the native side, and one will simply not find what the other holds. If a lookup returns nothing, switch explorers before assuming anything went wrong. Another frequent slip is copying an address with a stray space or a missing character; compare the first and last several characters of what you pasted with what the sender shows.
When you wait for an exchange deposit, ask the exchange for the transaction hash, open it, and read the status yourself. If the explorer shows success but your balance has not moved, the delay is on the exchange side, and the hash is exactly what its support team will ask for. If the explorer shows failure, the funds normally stay with the sender, minus the fee. Never rely on screenshots from strangers: anyone can edit an image, but nobody can edit a record you open yourself.
Explorers are also useful before you act. Opening a token contract tells you how old it is, how many holders it has and whether the activity looks organic. This does not prove safety, but a contract created hours ago with a handful of holders deserves caution. Treat the tracker on this page as a convenience; for anything of value, confirm on the explorers linked above.
Waiting on a deposit? Open a free account to move funds with confidence.
Open free accountFrequently asked questions
Does the tracker store my searches?
No. Queries go from your browser straight to the public RPC; this site has no backend.
