Identify the asset before the amount
ETH is Ethereum’s native asset. ERC-20 tokens use contract interfaces that include balance and transfer functionality. An NFT uses a different token standard and usually needs token-specific information such as a collection contract and token ID.
Write the network and asset next to the expected amount. A familiar ticker is not enough for a token investigation: use the contract address supplied by a verified project or the original transaction’s token details.
Follow the right evidence path
First check whether you expected native ETH or a token. For native ETH, Skooby’s recent movement view may answer your immediate question. For a token, open the linked explorer and select the token-transfer or token-holdings view.
For an NFT, inspect the collection and token ID in a suitable explorer. Do not value an unsolicited token or NFT simply because a page displays a large number next to it. A displayed name or balance does not establish a realizable sale price.
- Identify the exact network from the sending record.
- Write down the asset type: native coin, fungible token, or NFT.
- Use a token-aware explorer view when the asset is not native ETH.
- Compare the full recipient address and transaction record.
- Keep the native-ETH finding separate from the token finding.
Describe the limitation accurately
If Skooby returns no matching native movement, say “no matching movement in the loaded native ETH view.” Avoid saying “nothing arrived” until you have checked the asset’s own history.
This distinction also matters in exports. Skooby’s CSV contains the filtered native rows that were loaded. It does not turn that view into a complete token ledger or a complete portfolio report.
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.