Begin with the address and network
Use the full 0x address and select Ethereum. This version of Skooby queries Ethereum mainnet. The same address-shaped string may also appear on other EVM networks, so the address alone is not enough to identify where a payment happened.
Write down the network from the original withdrawal or sending record before you scan. If you are checking a transfer from an exchange, its withdrawal network is a better starting point than the coin’s ticker.
Turn a scan into a useful record
Read the scope notice next to the balance. Skooby currently shows native ETH, while ERC-20 tokens, NFTs, DeFi positions, and complete internal-call history are outside this scan. The explorer link gives you a next step when you need those other views.
- Paste the public address into Investigate and select Scan wallet.
- Use the date and direction filters to narrow the loaded movements.
- Open a transaction to inspect its hash, fee, block, and sender or recipient addresses.
- Choose Verify on explorer to compare the same transaction in Etherscan.
- Export the filtered rows if you need a copy of this particular view.
Explain gaps before making a conclusion
No rows in a filtered view means no matching rows in the data that was loaded. It does not prove that the address never transacted. Remove filters, check the recent-window notice, and inspect the full explorer history.
A token transfer can also happen without the native ETH movement you expected to see. Ethereum’s token documentation describes ERC-20 as a separate contract interface. For token questions, identify the contract and the network, then use a token-aware explorer view.
If you expected USDC but searched only the ETH timeline, record the result as “native ETH checked; token history still to review.” Do not label the payment missing yet.
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.