Identify the exact record first
Copy the full hash from the sending record or from Skooby’s movement details. Open the explorer link and confirm that you are looking at Ethereum mainnet. Then compare the full hash, not only its first and last few characters.
Ethereum’s transaction documentation describes fields such as sender, destination, nonce, ETH value, and gas limits. A destination may be a smart contract. It should not automatically be described as the final person receiving an asset.
Separate the movement from its cost
The ETH value and the network fee answer different questions. The first concerns native ETH attached to the transaction; the second concerns the cost of execution. Token activity may require reviewing the contract’s events or a token-transfer view.
When recording a transaction, put value and fee in separate columns. This avoids accidentally reporting the same fee as both an additional transfer and a separate expense. Keep the native amount alongside any USD estimate, and record the price timestamp if you add one.
Illustrative record: value 0.20 ETH; fee 0.00042 ETH. These are separate fields. A market price observed later would not establish the USD value at the moment of the transaction.
Use status and evidence together
A block number tells you where the record was included. Execution success is a separate question on Ethereum: an included contract call can have failed. Use the explorer’s execution status when that distinction matters; Skooby’s confirmation label is not a guarantee that every intended contract action succeeded.
Before sharing a conclusion, include the network, full hash, relevant addresses, amount units, and source link. A short explanation should say what you observed and what still needs verification. That is more useful than a screenshot with an unexplained large number.
Sources & scope
These guides combine Skooby product walkthroughs with the references below. Examples are illustrative. Skooby’s scans cover a limited recent window of native BTC or ETH activity.