~$ crypto-under-the-hood

# The machinery behind the coins

~/notes / reading on-chain data

Reading a Block Explorer Like an Analyst

Everything about a transaction is public. Knowing which fields matter turns an explorer from a status checker into an investigative tool.

Ivan Kruse · · 2 min

Most people use an explorer to check whether a transaction confirmed. It contains considerably more than that, and the additional fields answer most questions people ask in support channels.

The transaction page

Status. Success, failed, or pending. A failed transaction consumed gas and did nothing, which is the answer to a large share of “where are my funds” questions.

Block and confirmations. How deep the transaction is. Determines whether it is settled.

From and to. The to address is critical: if it is a contract rather than a wallet, the transaction did something beyond a transfer.

Value. Native asset moved. Zero for most token transfers, which confuses people, because the token movement appears further down.

Transaction fee and gas used. What you paid and how much work it required. Comparing gas used against the gas limit tells you whether it ran out.

Token transfers. A separate section listing tokens moved. For a swap this shows what went out and what came back, which is how you verify what you actually received.

Input data. The function called and its arguments. On verified contracts the explorer decodes this into readable form, which is how you confirm what a transaction actually did rather than what an interface said it would do.

The address page

Balance and token holdings. Current state.

Transaction history. Every interaction, permanently.

Analytics tabs. Several explorers show charts of activity over time.

Token approvals. The most practically important tab. It lists every contract with permission to move tokens from this address. Reviewing it periodically and revoking what you do not use is the single most valuable habit an explorer enables.

The contract page

Verified source code. If the developer published it and the explorer confirmed it compiles to the deployed bytecode. An unverified contract is one nobody can inspect, which is sufficient reason to avoid interacting with it.

Read and write functions. Lets you query the contract directly, which is how you check things like total supply or an owner address without trusting an interface.

Holders. Distribution of a token. The concentration question answered in thirty seconds.

Three investigations worth knowing how to do

Did my swap give me what I expected? Open the transaction, read the token transfers section, compare against what the interface quoted.

What can move my tokens? Address page, approvals tab, sorted by value at risk.

Is this token concentrated? Contract page, holders tab, look at the top ten excluding known pools and exchange addresses.

The limits

An explorer shows what happened, not who did it or why. Address labels are heuristic. Attribution of intent is inference.

And increasingly, activity happens where the chain does not see it: inside exchanges, inside custody structures, inside funds. An explorer is a complete record of on-chain events and a shrinking share of economically relevant ones.

That said, for the questions an individual actually has about their own transactions, it is complete and authoritative, and using it removes the need to ask anyone anything. A withdrawal from somewhere you can take custody straight away produces a hash you can follow through every stage described above, which is the fastest way to learn the tool on data you care about.

# Corrections and technical nitpicks are welcome. Send them over. They get published with the fix.

exploreranalysispractical

# related notes