The CATV tool requires users to input data into multiple fields before you could start tracking the transactions linked to a wallet address. What you should enter in these fields will be elaborated below.
1. Wallet Address: The wallet address of a valid Ethereum wallet. As of now, the CATV only supports Ethereum wallet addresses.
2. ERC20 Token Contract: By putting a token contract’s address in this text box, the CATV will track transactions involving the specific ERC20 token instead of Ethereum. For example, if a user wanted to track BNB transactions involving a particular wallet, he or she is required to enter the wallet address in the appropriate field and the BNB token’s contract address as well.
An ERC20 token’s contract address could be found on Etherscan.
Both the wallet address and the token contract address of the ERC20 token must be entered if users wish to see that specific ERC20 token’s transactions linked with the wallet address.
Take note that the results generated by CATV would only display transactions involving the ERC20 token in question if a token’s contract address is entered into this field. Ethereum transactions would not be visible in the graph nor will they be shown in the transaction list. If users only wish to see Ethereum-only transactions, then this field should be left blank.
3. Distribution Depth: This specifies how far would you like to trace the funds sent out by the wallet address. For example, a distribution depth of three will cause the graph to display the outgoing transactions, starting with the input wallet address, up to three hops away. The maximum distribution depth is ten.
4. Source Depth: The source depth is nearly identical to the distribution depth, except that it is for incoming transactions instead of outgoing ones. The maximum source depth is ten.
For example, if you are to search the input address “0x9b14Dd998023A024Fdd69249a8D961a66844105f” with a distribution and source depth of one, you would get the graph as seen above.
However, if you are to tweak the distribution and source depth to two, you would see this graph instead.
5. Date Range: This filters the transactions only in the first hop for both distribution and source. Hence, the initial outgoing and incoming hops will only display transactions made during the specified time period in the graph.
6. Force Lookup: This checkbox forces the tool to not return any cached results. Instead, it makes an API call and pulls the most updated results, in exchange for longer load times for them to be displayed
In order to obtain the ideal results, these tips are advisable before you click the “Start Tracking” button:
Please try to keep your depths to 5 and below if possible. While the maximum limit is 10, under 5 and below is recommended for better speed and a graph output that is readable.
For wallet addresses that are highly active, use the Date Range filter to narrow the search down to only the day(s) of interest.
If you are experiencing slow loading time, you can consider doing source and depth search separately by setting either to zero. This might be caused by the type of wallet. For example, splitter wallets would have a few incoming transactions and many outgoing transactions.
Once you’re done with setting the fields to your desired values and ready to start tracking, simply click on the ‘Start Tracking’ button to have the tool begin generating the graph.