The fields that actually matter, in plain terms
| Field | What it means |
|---|---|
| Hash | The transaction's unique ID, use this to look it up anywhere |
| Status | Success or failed. A failed transaction still costs gas but did nothing else |
| From / To | The sending wallet, and the recipient, a wallet address or a contract address |
| Value | How much native currency (ETH) was sent directly with the transaction |
| Gas used / Gas price | The computational cost paid to execute it, and the rate paid per unit |
| Method | Which contract function was called, if it's a contract interaction, not a plain transfer |
Internal transactions: the part beginners usually miss
A single top-level transaction can trigger a contract to call other contracts internally, deploy new contracts, or move funds in ways that never show up in the simple "value" field. This is exactly how a token launch works: your one transaction to a launch factory can internally create a brand-new token contract, all within that same top-level transaction. If you only look at the top-level from/to/value, you'll miss what actually happened. Check the "internal transactions" tab for the full picture.
Logs and events: what actually got recorded
Contracts emit events (logged on-chain, cheaper than storage) to record that something specific happened, a transfer, a swap, a new token being launched. A well-built explorer decodes these into readable form when it recognizes the event shape, showing you the actual token addresses, amounts, and parties involved, not just raw hex data. This is exactly what a token-launch factory's log looks like when a new coin is created, and it's how automated tools (including ScanHood's own collectors) discover new launches in the first place, by watching these logs.
A quick walkthrough
ScanHood's own /explorer covers all of this for Robinhood Chain specifically, with a safety scan and market data layered on top of the raw transaction view.
Frequently asked
Why would a transaction show ETH value as zero but still do something significant?
Because the actual action (a token launch, a swap, an NFT mint) is usually driven by the transaction's input data and internal calls, not by sending ETH directly in the top-level value field. A zero-value transaction that calls a contract function can still move enormous amounts of value internally.
What does it mean if a transaction succeeded but I don't see the result I expected?
Check the logs and internal transactions carefully, the transaction may have executed a different path than expected (for example, a swap that returned less output than assumed due to slippage) without technically failing. "Success" means the code ran without reverting, not that it produced the outcome you assumed.
Can a failed transaction still cost money?
Yes. Gas is spent on the computation attempted up to the point of failure, even if the transaction ultimately reverts and no state change persists. This is why a failed transaction still shows a gas cost.
Is reading raw transactions necessary if I'm just trading, not building?
Not for routine trades, but it's genuinely useful when something looks off, an unexpected result, or before trusting a claim about what a contract does. Being able to check the actual on-chain record yourself, rather than relying entirely on a project's word, is a real safety skill.