# What Is a Blockchain Explorer and How Do You Use One?

![Terenval Wallet beside a blockchain explorer showing a transaction hash, confirmations, sender, recipient and token transfer details](hero.webp)

**A blockchain explorer is a public search interface for blockchain data.** It lets you look up transactions, blocks, addresses, token transfers, fees and other onchain activity without giving the explorer control of your wallet.

The most important rule is to **choose the correct blockchain first**. A transaction hash from Ethereum must be checked on an Ethereum-compatible view of that transaction, while a Bitcoin transaction must be checked on a Bitcoin explorer. Searching the right identifier on the wrong network can make a real transaction appear to be missing.

> **Short answer:** To use a blockchain explorer, open a trusted explorer for the exact network, paste a public transaction hash or address, and verify the status, sender, recipient, amount, token contract where relevant, fee, block and confirmation information. Never enter a seed phrase, private key or wallet password. An explorer reads public blockchain data; it does not need your recovery secrets.

This guide focuses on **verification and troubleshooting**, not on one specific explorer website. Interfaces differ, but the underlying questions are broadly the same.

## Key Takeaways

- **A blockchain explorer reads public onchain data.** It is not your wallet and does not need your private key or recovery phrase.
- **Network selection comes first.** The same-looking address or transaction identifier can be meaningless on the wrong chain.
- **A transaction hash is usually the best lookup key.** It identifies one specific transaction more precisely than searching an address.
- **“Success” has a narrow meaning.** It can mean the transaction executed without reverting, not that you used the intended network, token or recipient.
- **Token transfers may not match the top-level `to` field.** On EVM networks, a token transfer can involve a smart contract while the actual recipient appears in token-transfer logs.
- **Confirmations matter.** A transaction included in a block gains stronger settlement confidence as more blocks or finality conditions accumulate.
- **Explorer labels are not the blockchain itself.** Names, tags, token prices, decoded method labels and risk notices can come from the explorer's own indexing or metadata.
- **Public data is not private data.** Addresses and transaction histories are visible on public blockchains, but seed phrases and private keys must never be entered into an explorer.

## What Is a Blockchain Explorer?

A blockchain explorer is software that organizes blockchain data into a searchable interface. [Ethereum.org describes block explorers](https://ethereum.org/developers/docs/data-and-analytics/block-explorers/) as portals to data about blocks, transactions, validators, accounts and other onchain activity.

The blockchain itself is maintained by the network's nodes and consensus rules. The explorer is an **observation layer**: it retrieves, indexes, decodes and presents data in a form that people can search.

That distinction matters. If one explorer is unavailable, delayed or displays a confusing label, the blockchain does not stop. You can compare another explorer, query a node or use other trusted network tooling.

A typical explorer can answer questions such as:

| Question | What to search |
|---|---|
| Did my transaction reach the network? | Transaction hash / TXID |
| Was it included in a block? | Transaction hash |
| How many confirmations does it have? | Transaction hash |
| Which address received funds? | Transaction hash |
| What is the history of this public address? | Address |
| Which token contract was involved? | Transaction hash or token contract |
| What fee was paid? | Transaction hash |
| Which transactions are in a block? | Block number or block hash |
| Is a smart contract verified or labeled? | Contract address |

An explorer can make public chain data easier to interpret, but it does not change ownership, reverse transactions or move funds between networks.

## Blockchain Explorer vs Wallet: What Is the Difference?

A **wallet** manages the information and signing process required to control blockchain accounts. A **blockchain explorer** displays public network data.

Think of the difference this way:

- A wallet can prepare and sign a transaction.
- The network validates and records the transaction according to its rules.
- An explorer helps you inspect the public result.

A legitimate explorer does not need your seed phrase to show a transaction. It does not need your private key to search an address. It does not need your wallet password to display a block.

If a website presented as a “block explorer” asks you to enter recovery words to view a transaction, treat that as a major security warning.

For the wallet side of the distinction, see [What Is a Crypto Wallet and What Does It Store?](https://wallet.terenval.com/answers/what-is-a-crypto-wallet-and-what-does-it-store/).

## What Can You Search on a Blockchain Explorer?

The exact search field depends on the network and explorer, but several identifiers appear repeatedly.

### Transaction hash or TXID

A transaction hash is a public identifier for a particular transaction. On many networks, this is the most precise way to inspect a transfer because it takes you directly to the transaction record.

A transaction hash is **not a secret**. Support teams can often use it to investigate a public transaction without needing any recovery material.

### Wallet or account address

An address search normally shows public activity associated with that address. On Ethereum and EVM networks, an account page can show native-asset balances, token balances and transaction history. [Ethereum.org's explorer documentation](https://ethereum.org/developers/docs/data-and-analytics/block-explorers/) lists account addresses, balances, tokens and transaction history among common explorer data.

An address search is broader than a transaction-hash search. It may include many unrelated past transactions, internal operations or token transfers.

### Block number or block hash

A block page can show when a block was produced, which transactions it includes and network-specific metadata. This is useful when you need to establish exactly where a transaction was included.

### Smart-contract address

On smart-contract networks, searching a contract address may show bytecode, verified source code when available, token metadata, contract events and transaction history.

Do not confuse a **token contract address** with your **personal receiving address**. A token contract identifies the token program; your receiving address identifies the account or destination that receives or controls assets.

## How to Check a Crypto Transaction Step by Step

Use the following sequence whenever you need to verify whether a transaction actually happened.

### 1. Identify the exact network

Before opening an explorer, establish the network used for the transaction.

Examples include:

- Bitcoin Mainnet
- Ethereum Mainnet
- Base
- Arbitrum One
- OP Mainnet

Do not assume that a `0x` address identifies Ethereum Mainnet. The same key-controlled EVM address can appear on multiple EVM networks with separate balances and histories.

If you are checking an exchange withdrawal, start with the exchange's recorded withdrawal network. If you are checking a wallet transfer, use the network selected when the transaction was signed.

For a full explanation, see [How to Choose the Correct Network When Withdrawing Crypto From an Exchange](https://wallet.terenval.com/answers/how-to-choose-the-correct-network-when-withdrawing-crypto-from-an-exchange/).

### 2. Copy the transaction hash from a trusted source

Prefer the transaction hash displayed by your wallet, exchange withdrawal record or receiving service.

Do not use a hash sent by an unsolicited support account unless you independently confirm that it belongs to your transaction.

Copy the entire identifier. A transaction hash is safer for diagnosis than trying to infer the transaction from an address and approximate time.

### 3. Open a trusted explorer for that network

Use an explorer linked from the network's official documentation, a well-established explorer you independently know, or another trusted source.

Check the domain carefully. Search ads, copied interfaces and look-alike domains can be used for phishing.

A normal explorer lookup should not require you to:

- connect a wallet merely to view public data;
- sign a message;
- approve a token;
- install a browser extension;
- enter a recovery phrase;
- enter a private key.

### 4. Search the transaction hash

Paste the public hash into the explorer search field.

You should then see a transaction page or a clear “not found” result. If the explorer cannot find it, do not immediately conclude that the funds are lost. First verify the network and whether the transaction was actually broadcast.

### 5. Read the transaction status

Common states include **pending**, **success/confirmed** and **failed/reverted**, although wording differs by network and explorer.

On Ethereum, [transaction data](https://ethereum.org/developers/docs/data-and-analytics/block-explorers/) commonly includes status, block, timestamp, sender, recipient, transferred tokens, value and transaction fee.

Interpret status narrowly:

- **Pending:** the transaction has been broadcast or observed but has not yet reached the explorer's confirmed state.
- **Success:** the transaction was included and its execution succeeded according to that network's rules.
- **Failed / reverted:** the attempted state change did not complete successfully.

A successful status does **not** prove that you chose the right network or token. It also does not prove that an exchange will credit a deposit sent through an unsupported route.

### 6. Verify sender, destination and actual asset movement

Compare the public details with what you intended.

Check:

- sender address;
- receiving address or relevant contract;
- native-asset amount;
- token transfer amount;
- token contract;
- network;
- timestamp;
- transaction fee.

For a simple native-asset transfer, the top-level sender and recipient may be enough. For a token transfer or dApp interaction, you need more context.

### 7. Check the block and confirmation information

Once a transaction is included in a block, explorers normally display its block number and some form of confirmation or finality information.

Do not use one universal “safe number of confirmations” for every blockchain. Settlement models differ.

For Bitcoin, [Bitcoin.org explains](https://bitcoin.org/en/how-it-works) that confirmed transactions are recorded in the blockchain, while the [Bitcoin payment-processing guide](https://developer.bitcoin.org/devguide/payment_processing.html) explains how additional blocks increase confidence against replacement of transaction history.

For Ethereum and proof-of-stake networks, explorers may show block inclusion and separate finalized status or related consensus information. Use the network's own settlement model rather than importing Bitcoin terminology mechanically.

## How to Read an Ethereum or EVM Transaction

Ethereum and EVM explorers often expose more fields than a simple payment receipt because a transaction can call a smart contract and trigger multiple token transfers or events.

### Transaction hash

This identifies the submitted transaction.

Use it as the primary reference when communicating with support. A screenshot alone is less precise because it may omit the network, hash or full addresses.

### Status

A successful EVM transaction means execution did not revert. A failed transaction can still consume gas because network computation was performed before the failure became final.

### From

The `from` address is the account that submitted the transaction.

### To

The top-level `to` field can be:

- another user account;
- a token contract;
- a router;
- a bridge contract;
- a decentralized exchange contract;
- another smart contract.

This is why **the top-level `to` field is not always the final token recipient**.

If you sent an ERC-20 token, inspect the explorer's token-transfer section, logs or decoded events. A token contract may be the top-level interaction target while the transfer event identifies the actual recipient and amount.

### Value

On Ethereum, the top-level value is the amount of native ETH attached to the transaction.

It is not automatically the amount of an ERC-20 token transfer. A token transfer can have a top-level ETH value of zero while moving tokens through contract state changes.

### Transaction fee and gas

Ethereum transaction fees depend on gas usage and fee parameters. [Ethereum.org's gas documentation](https://ethereum.org/developers/docs/gas/) explains that gas measures computational work and that fees are paid in ETH.

When troubleshooting, distinguish:

- gas limit;
- gas used;
- fee parameters;
- total transaction fee.

A failed smart-contract call may still have a non-zero transaction fee.

### Input data and method

A smart-contract transaction can contain encoded input data. Explorers may decode that input into a human-readable method name when they know the contract interface.

Treat decoded method labels as an interpretation layer. The actual signed input data is the underlying transaction data; an explorer's friendly description can depend on verified metadata and decoding.

## Why “Success” Does Not Always Mean “Everything Is Correct”

This is one of the most important explorer concepts.

Suppose you intended to send USDC to an exchange deposit on Ethereum, but you actually sent USDC on Base to the same-looking destination address.

The Base explorer may correctly show:

- status: success;
- token transfer: completed;
- recipient: the address you entered.

The explorer is not saying the receiving exchange supports that deposit route. It is saying the Base transaction executed successfully.

Similarly, a successful interaction with a malicious or unintended smart contract is still technically successful if the network executed the signed instructions.

**Explorer status answers a protocol question, not every business or user-intent question.**

To validate the intended result, you may also need to verify:

- correct blockchain;
- correct token contract;
- correct recipient;
- correct amount;
- receiving service support;
- expected application state.

## How to Read a Bitcoin Transaction Explorer

Bitcoin transaction views differ from Ethereum because Bitcoin uses the UTXO model rather than Ethereum-style account state.

[Bitcoin's developer documentation](https://developer.bitcoin.org/devguide/transactions.html) describes transactions as spending previous outputs and creating new outputs.

A Bitcoin explorer commonly shows:

- TXID;
- transaction status;
- block or confirmation count;
- inputs;
- outputs;
- amounts;
- transaction fee;
- size or virtual size.

### Inputs and outputs

A Bitcoin transaction can have multiple inputs and multiple outputs. One output may pay the intended recipient while another returns **change** controlled by the sender's wallet.

That means a list of outputs should not automatically be interpreted as “all of these are separate payments to other people.”

When verifying a payment, identify the specific output address and amount you expected.

### Confirmations

A Bitcoin transaction gets its first confirmation when it is included in a block. Additional blocks increase the amount of work that would need to be replaced to reorganize that transaction's history.

The appropriate confirmation threshold depends on the value and risk context. Do not treat “six confirmations” as a universal rule for every asset, network or payment size.

### Fees

Bitcoin transaction fees relate to transaction data size and fee-market conditions rather than an Ethereum-style gas execution model.

Do not compare a Bitcoin fee field directly with Ethereum gas fields as if they measured the same mechanism.

## What Does “Pending” Mean on a Blockchain Explorer?

A pending transaction has not yet reached the explorer's confirmed or finalized state.

Possible reasons vary by network.

On an EVM network, a transaction can remain pending because its fee is unattractive relative to current conditions, an earlier transaction from the same account and nonce sequence is still unresolved, or the explorer has not yet reflected the latest network state.

On Bitcoin, an unconfirmed transaction may remain outside a block while miners prioritize other transactions.

When a transaction is pending:

1. Confirm that you are viewing the correct network.
2. Confirm the exact transaction hash.
3. Check whether the wallet shows a replacement, cancellation or newer transaction.
4. Review the explorer's fee and nonce information where relevant.
5. Avoid repeatedly submitting unrelated transactions without understanding the account's pending state.

Do not send a seed phrase to “speed up” a transaction. Recovery secrets have no legitimate role in an explorer's public transaction lookup.

## What If the Explorer Says “Transaction Not Found”?

“Not found” is a diagnostic clue, not a complete diagnosis.

Check these possibilities:

| Possible cause | What to check |
|---|---|
| Wrong blockchain explorer | Verify the actual sending network |
| Transaction was never broadcast | Check the wallet or exchange record |
| Hash was copied incorrectly | Copy the complete hash again |
| Explorer indexing is delayed | Compare another trusted explorer |
| Transaction was replaced | Check wallet history and related nonce/transaction data |
| You have an internal exchange reference, not an onchain hash | Look for the actual TXID / transaction hash |

If an exchange marks a withdrawal “completed” but provides no usable onchain transaction hash, consult the exchange's official support information. Do not substitute a random blockchain transaction found by searching the amount.

## How to Verify a Token Transfer Correctly

Token transfers are a frequent source of explorer mistakes.

For an EVM token, verify **all of these**:

1. **Network:** Ethereum, Base, Arbitrum One or another exact chain.
2. **Token contract:** the exact contract representing the asset on that chain.
3. **Recipient:** the intended destination address.
4. **Amount:** account for token decimals and the explorer's formatted display.
5. **Transfer event:** inspect the token-transfer section rather than relying only on top-level ETH value.
6. **Transaction status:** confirm that the transaction succeeded.

A familiar token symbol or logo is not enough. An unrelated contract can use the same name or ticker.

If the blockchain shows the token at your address but the wallet interface does not, the issue may be display or token-detection related rather than an onchain transfer failure. See [Why a Token Can Be Missing From a Wallet Even When the Blockchain Shows It](https://wallet.terenval.com/answers/token-missing-from-wallet-blockchain-shows-it/).

## How to Use a Block Explorer After an Exchange Withdrawal

An explorer is one of the best independent tools for checking whether an exchange withdrawal reached the blockchain.

After the exchange says the withdrawal was sent:

1. Record the exact withdrawal network.
2. Copy the onchain transaction hash.
3. Open a trusted explorer for that network.
4. Check transaction status.
5. Compare the full destination address.
6. Verify the transferred asset and amount.
7. For tokens, verify the contract and transfer event.
8. Check block inclusion and confirmations.
9. Confirm the wallet or receiving service recognizes the same transfer.

If this is a new withdrawal route, a small test transaction can reduce the impact of some mistakes. Read [Should You Send a Small Test Transaction Before a Large Transfer?](https://wallet.terenval.com/answers/should-you-send-small-test-transaction-before-large-transfer/) for what a test can and cannot prove.

## How to Use a Blockchain Explorer With Terenval Wallet

[Terenval Wallet](https://wallet.terenval.com/?lang=en) is an installable self-custody wallet for Android with Bitcoin, Ethereum and supported EVM/L2 networks. Its [supported-networks documentation](https://wallet.terenval.com/info/supported-networks/) should be used to confirm the network context before interpreting a transaction.

A practical verification workflow is:

1. In Terenval, identify the account and network involved in the transfer.
2. Copy the public receiving address or transaction hash relevant to the transaction.
3. Open a trusted explorer for that exact network.
4. Verify the public onchain record independently from the wallet interface.
5. Compare the address, asset, amount and status.
6. If the wallet display and explorer disagree, do not expose recovery material; investigate network selection, token metadata and wallet indexing first.

**Want to prepare a self-custody wallet on Android?** [Open or install Terenval Wallet](https://wallet.terenval.com/?lang=en), and review the [product overview](https://wallet.terenval.com/about/) and [security documentation](https://wallet.terenval.com/info/security/) before depositing meaningful funds.

An explorer is separate from Terenval Wallet. Public transaction verification does not require giving the explorer control of your wallet.

## What a Blockchain Explorer Can Prove — and What It Cannot

A high-quality explorer is useful evidence, but the wording “the explorer proves it” can be too broad.

### What it can help establish

An explorer can help establish that public chain data contains:

- a particular transaction hash;
- a sender and transaction destination;
- a block inclusion;
- a token transfer event;
- a public address balance or history as indexed;
- a transaction fee;
- a smart-contract interaction;
- confirmation or finality-related data.

### What it does not automatically prove

An explorer does not automatically prove:

- that you personally control an address;
- that a labeled address truly belongs to the named organization;
- that a token with a familiar ticker is authentic;
- that a verified smart contract is economically safe;
- that a receiving exchange supports the network you used;
- that a transaction matched your original intent;
- that an explorer's price estimate or name tag is consensus data.

For ownership, an address label is weaker evidence than control demonstrated through an appropriate signing process. For token authenticity, use issuer or project documentation and verify the contract address.

## Are Blockchain Explorer Labels Always Reliable?

No. Separate **onchain facts** from **explorer-added interpretation**.

Onchain facts include items such as transaction hashes, addresses, block data and contract bytecode as represented by the network.

Explorer-added information can include:

- address name tags;
- phishing warnings;
- token logos;
- token prices;
- portfolio valuations;
- decoded method names;
- contract labels;
- categorization of transactions.

These additions can be extremely useful, but they may come from external databases, verified-source submissions, heuristics or third-party data.

Use labels as context, not as a replacement for checking the underlying address, network and transaction.

## Is It Safe to Paste a Wallet Address Into a Block Explorer?

A public wallet address or transaction hash is not a signing secret, so it can be searched without granting spending authority.

However, public does not mean private. A blockchain address can expose transaction history and balances, and a hosted website may be able to observe normal web metadata associated with your visit.

For better privacy hygiene:

- avoid unnecessarily sharing addresses publicly;
- do not paste addresses into unrelated websites;
- use explorers you trust;
- consider whether repeated address searches reveal information about your interests;
- never confuse a public address with a private key.

Most importantly, **never paste a seed phrase or private key into a blockchain explorer**.

## Common Blockchain Explorer Mistakes

### Mistake 1: Searching on the wrong network

A Base transaction will not become an Ethereum Mainnet transaction because both networks use `0x` addresses.

Check the sending network first.

### Mistake 2: Looking only at the top-level `to` address

For token transfers and dApp transactions, the top-level target can be a contract.

Inspect token transfers, logs and decoded interaction details.

### Mistake 3: Assuming “success” means the receiving service credited the deposit

A transaction can succeed onchain while violating an exchange's deposit instructions.

Check the receiving service's supported network and token.

### Mistake 4: Trusting a ticker instead of the token contract

A token called “USDC” or “USDT” is not authentic merely because the explorer interface shows that symbol.

Verify the contract through an authoritative source.

### Mistake 5: Treating address labels as absolute proof of identity

Explorer tags are helpful but can depend on offchain attribution.

Compare official deposit information or documented addresses when identity matters.

### Mistake 6: Sharing recovery material with “support”

A support person who has a transaction hash and public address can inspect the same public data you can.

They do not need your seed phrase to read an explorer.

## A Practical Explorer Troubleshooting Table

| What you see | Likely interpretation | Next check |
|---|---|---|
| Transaction found and successful | The network executed the transaction successfully | Verify asset, recipient, token contract and intended network |
| Transaction found but pending | Not yet confirmed/final in the expected way | Check fees, nonce/state and network conditions |
| Transaction failed/reverted | The intended EVM state change did not complete | Check error context and fee spent; do not blindly resubmit |
| Transaction not found | Wrong network, bad hash, no broadcast, replacement or indexing delay | Verify network and source of the hash |
| Correct token transfer onchain but wallet shows zero | Possible wallet display/network/token-detection issue | Verify account, chain and token metadata |
| Correct address but wrong chain | Assets exist on a different network than intended | Follow network-specific recovery guidance; do not assume switching display moves them |
| Exchange withdrawal says complete but no TXID | May still be an internal/custodial processing issue | Request the actual onchain transaction reference |
| Explorer shows suspicious token | Could be unsolicited spam or unrelated token contract | Do not interact; verify issuer and contract independently |

## Blockchain Explorer Checklist

Before you rely on an explorer result, confirm:

- I know the exact blockchain or network.
- I copied the complete transaction hash from a trusted source.
- I am using a trusted explorer for that network.
- I checked the sender and intended recipient.
- I checked the actual transferred asset.
- For tokens, I verified the contract address.
- I inspected token transfers or logs when a smart contract is involved.
- I checked block inclusion and confirmation/finality information.
- I distinguished network data from explorer-added labels and prices.
- I did not enter a seed phrase, private key or wallet password.
- I understand that transaction success does not prove the route matched my intended use.

## Frequently Asked Questions

### What is a blockchain explorer?

A blockchain explorer is a searchable interface for public blockchain data. It can display transactions, blocks, addresses, balances, token transfers, fees, smart-contract activity and other network-specific information.

### How do I track a crypto transaction?

Find the transaction hash or TXID, identify the exact network, open a trusted explorer for that network and search the hash. Then check status, sender, recipient, amount, asset, fee, block and confirmations.

### Is a transaction hash safe to share?

A transaction hash is public blockchain information and does not provide signing authority. Sharing it can still reveal transaction details and associated addresses, so consider the privacy context, but it is not comparable to sharing a private key or seed phrase.

### Can someone steal my crypto with only my transaction hash?

A transaction hash by itself does not provide the private signing key needed to spend from your wallet. It can reveal public transaction details, so it should not be confused with a privacy guarantee.

### Why does my transaction say “success” but the funds are missing?

You may be viewing the wrong network in the wallet, the token may not be displayed automatically, the receiving service may not support the route, or the transaction may have interacted with a contract in a way you did not expect. Verify the network, recipient, token contract and actual transfer events.

### Why is my transaction not showing on the explorer?

Common reasons include using the wrong network explorer, copying the wrong identifier, the transaction never being broadcast, an explorer indexing delay or replacement of a pending transaction. Confirm the network and source of the hash first.

### How many confirmations do I need?

There is no universal number for every blockchain and use case. Bitcoin confirmation practices differ from Ethereum proof-of-stake finality and from other networks. Follow the network and receiving service's risk requirements.

### Does a blockchain explorer know my seed phrase?

No legitimate explorer needs your seed phrase to display public onchain data. If a site asks for recovery words or a private key to “find” or “verify” a transaction, do not provide them.

### Can a blockchain explorer reverse a transaction?

No. An explorer is an observation interface. It cannot reverse a confirmed blockchain transaction merely by changing what it displays.

### Is a verified smart contract on an explorer safe?

Not necessarily. Verified source code can help users inspect whether published source corresponds to deployed bytecode under the explorer's verification process, but it does not prove that the contract is economically safe, free of malicious logic or appropriate for your use.

### Why does an ERC-20 transfer show the token contract in the `to` field?

The top-level transaction can call the token contract, while the contract updates token balances and emits a transfer event identifying the token sender and recipient. Inspect the token-transfer section or logs rather than treating the top-level `to` field as the final token recipient.

### Can I search the same Ethereum address on Base or Arbitrum?

A conventional EVM account can have the same address on multiple EVM chains, but each chain has separate state, balances and transaction history. Search the address on the specific network you want to inspect. See [Why the Same Ethereum Address Works on Multiple EVM Networks](https://wallet.terenval.com/answers/same-ethereum-address-multiple-evm-networks/).

## Key Terms

- **Blockchain explorer:** A searchable interface that indexes and displays public blockchain data.
- **Transaction hash / TXID:** A public identifier for a specific transaction.
- **Confirmation:** Evidence that a transaction has been included in blockchain history, with network-specific confidence increasing as settlement progresses.
- **Block:** A network data structure containing transactions and other protocol information.
- **Token contract:** A smart contract representing a token on a specific smart-contract network.
- **Gas:** The measurement used for computational work in Ethereum and EVM transactions; transaction fees depend on gas usage and fee parameters.
- [Wallet address](https://wallet.terenval.com/glossary/wallet-address/): Public receiving or account information used to identify an onchain destination or account.
- [Non-custodial wallet](https://wallet.terenval.com/glossary/non-custodial-wallet/): A wallet arrangement in which the user controls the relevant signing access.

## Related Terenval Answers

- [How to Choose the Correct Network When Withdrawing Crypto From an Exchange](https://wallet.terenval.com/answers/how-to-choose-the-correct-network-when-withdrawing-crypto-from-an-exchange/)
- [Should You Send a Small Test Transaction Before a Large Transfer?](https://wallet.terenval.com/answers/should-you-send-small-test-transaction-before-large-transfer/)
- [Why a Token Can Be Missing From a Wallet Even When the Blockchain Shows It](https://wallet.terenval.com/answers/token-missing-from-wallet-blockchain-shows-it/)
- [Why the Same Ethereum Address Works on Multiple EVM Networks](https://wallet.terenval.com/answers/same-ethereum-address-multiple-evm-networks/)
- [What Is a Crypto Wallet and What Does It Store?](https://wallet.terenval.com/answers/what-is-a-crypto-wallet-and-what-does-it-store/)

## Primary and Authoritative Sources

- [Ethereum.org — Block Explorers](https://ethereum.org/developers/docs/data-and-analytics/block-explorers/)
- [Ethereum.org — Transactions](https://ethereum.org/developers/docs/transactions/)
- [Ethereum.org — Accounts](https://ethereum.org/developers/docs/accounts/)
- [Ethereum.org — Gas and Fees](https://ethereum.org/developers/docs/gas/)
- [Ethereum.org — Interacting With Smart Contracts](https://ethereum.org/developers/docs/smart-contracts/interacting/)
- [Bitcoin.org — How Bitcoin Works](https://bitcoin.org/en/how-it-works)
- [Bitcoin Developer Guide — Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html)
- [Bitcoin Developer Guide — Transactions](https://developer.bitcoin.org/devguide/transactions.html)
- [Terenval Wallet — Supported Networks](https://wallet.terenval.com/info/supported-networks/)
- [Terenval Wallet — Official Product Overview](https://wallet.terenval.com/about/)
- [Terenval Wallet — Security and Non-Custodial Design](https://wallet.terenval.com/info/security/)

*Editorial note: General technical statements were checked against the primary and authoritative documentation linked above. Explorer interfaces, labels, indexing speed, token metadata, fees and network conditions can change, so users should verify live information at the time of a transaction. Explorer-added labels and valuations are not necessarily consensus data. Terenval product statements are first-party, and install links are promotional. This guide is educational, not individualized financial advice, and does not guarantee the safety, authenticity or availability of any explorer, wallet, token, network or service.*

## Editorial & technical review

- Published by: Terenval
- Technical review: Terenval Wallet team
- Last reviewed: 2026-10-16

## Sources

- [Ethereum.org — Block Explorers](https://ethereum.org/developers/docs/data-and-analytics/block-explorers/)
- [Ethereum.org — Transactions](https://ethereum.org/developers/docs/transactions/)
- [Ethereum.org — Accounts](https://ethereum.org/developers/docs/accounts/)
- [Ethereum.org — Gas and Fees](https://ethereum.org/developers/docs/gas/)
- [Ethereum.org — Interacting With Smart Contracts](https://ethereum.org/developers/docs/smart-contracts/interacting/)
- [Bitcoin.org — How Bitcoin Works](https://bitcoin.org/en/how-it-works)
- [Bitcoin Developer Guide — Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html)
- [Bitcoin Developer Guide — Transactions](https://developer.bitcoin.org/devguide/transactions.html)
- [Terenval Wallet — Supported Networks](https://wallet.terenval.com/info/supported-networks/)
- [Terenval Wallet — Official Product Overview](https://wallet.terenval.com/about/)
- [Terenval Wallet — Security and Non-Custodial Design](https://wallet.terenval.com/info/security/)

Official article: https://wallet.terenval.com/answers/what-is-a-blockchain-explorer-and-how-do-you-use-one/

[Machine-oriented Terenval index](https://wallet.terenval.com/llms.txt)
