Welcome to CoinDropster
Enter a new password
Choose a new password
Enter a new password for your account.
All active sessions will be signed out.
By clicking “Sign in”, you confirm that you have read and agree to the CoinDropster Terms of Use, Privacy Policy and Disclaimer
How to Read a Block Explorer: Address, Transaction, Contract
How to use a block explorer: address vs transaction vs contract, reading status and fees, checking a claim, approvals and a token's contract address.
Learning how to use a block explorer (Etherscan or the equivalent for your network) is a core skill for anyone dealing with airdrops: it shows what actually happened to your funds, not what a website interface displays. This article covers what an explorer page contains, how to tell an address from a transaction and a contract, and how to check a claim and a token.
This material is educational and is not financial or legal advice. It does not guarantee protection from loss: an explorer shows blockchain data but does not judge its safety for you.
Address, transaction, contract: three different pages
A block explorer is a search engine for public blockchain data. Whatever you paste into it is one of three things.
- Address — an account identifier: 0x followed by 40 hexadecimal characters. It can be your wallet, someone else's wallet or a smart contract. The page shows the balance, activity history and token tabs.
- Transaction — one specific operation. Its identifier, the transaction hash, is longer: 0x and 64 characters. You can copy the hash from your wallet or a site interface and paste it into search to see the outcome without intermediaries.
- Contract — an address where program code is deployed. Tokens, pools and claim pages all run through contracts. A contract page has extra tabs for code and functions.
A common mix-up: a token's address is the address of its contract, not the address of the "project owner". This matters later when checking for fakes.
How to read a transaction page
Open any of your own transactions and find the main fields.
- Status. There are usually three states: success, failed and pending. Pending means the operation is not yet included in a block. Failed means execution was reverted and nothing changed, but the fee for the gas used is still charged. Success only means the transaction executed, not that the result is good for you.
- From and To. From is the address that sent the transaction (usually yours). To is the recipient of the call. For a claim, To should be the claim contract, not a random address. For a token transfer, To is the token contract, and the real recipient is inside the operation data.
- Fee. This is gas used multiplied by gas price; the explorer shows the total in the network's coin. How it is formed is covered in the article on gas fees.
- Time and block number. These help match the operation to the moment you clicked the button.
- Input data. This shows which function was called. For an ordinary user it is a reference detail, but the function name sometimes reveals what was done: transfer, approval, claim.
Token transfers that happened inside the transaction are shown here too. They reveal the real outcome: who sent what to whom.
Address tabs: tokens, transfers, permissions
Your own address page usually has several tabs.
- Transactions. Regular operations sent from this address.
- Internal transactions. Transfers of the network's coin that happened inside a contract call. An ordinary transaction may not show an incoming amount, but it is visible here.
- Token transfers. Separate lists for tokens and NFTs. If a token arrived at the address, it appears here even when the wallet does not display it. This is also how you can spot unfamiliar tokens, covered in the article on an unknown token in your wallet.
- Permissions (approvals). If your explorer has such a section, it shows which addresses you allowed to spend your tokens and how much. An unlimited permission for a long-forgotten site is a reason to review it. How to revoke what you do not need is described in the article on revoking token approvals.
How to assess a contract: verification, age, activity
Before interacting with an unfamiliar contract, open its page and check a few things.
- Verification. If the contract tab shows published source code marked as verified, the code matches the deployed bytecode and can be read. That is transparency, not a safety guarantee: a verified contract can still contain dangerous functions or bugs. A lack of verification is a reason for caution, because the logic cannot be checked.
- Age. See when the contract was created and when its first operation happened. A fresh contract that "everyone is already talking about" needs extra checking.
- Activity. A real project usually shows many different addresses and regular operations. A contract with almost no history, or with operations from only a few addresses, is not necessarily a scam, but it is no reason to trust blindly.
- Creator. The page shows the address that deployed the contract. Compare it with what the project's official documentation states.
How to verify a claim and spot a fake token
To confirm a claim arrived, find its hash in your wallet history and open it in the explorer. Check in order: status is success, To is the contract given in the project's official documentation, and the token transfers inside the transaction include an incoming one to your address. If the token is missing from the wallet but the transfer is in the explorer, it is most likely a display issue: add the token manually using the contract address. The general claim procedure is described in the article on claiming an airdrop safely.
A fake token is given away not by its name or logo, which anyone can copy, but by its contract address. Two tokens with the same ticker can be entirely different contracts. Compare the address with the one published in the project's official documentation, not with what a link from a chat or an ad shows. If the addresses differ by even one character, it is a different token.
The same principle applies to a claim site: it is best to combine the signs of fake pages with a contract check in the explorer.
In the CoinDropster catalog every project has a page with its status and key facts, and status changes (Potential, Confirmed, Snapshot, Verification, Reward available or Distributed) are tracked. This helps you understand whether a distribution is expected at all: if the status does not imply a claim yet, any "contract to receive tokens" deserves especially careful checking. In-app checklists keep deadlines at hand so you do not act in a rush. View tracked airdrops →