ProtocolScout is a "non-custodial" blockchain explorer in the sense that your requests for raw on-chain data do not "travel" across our servers/nodes. Instead, we deliver into your browser configurations and provide it with processing code so that your browser can retrieve chain data from various providers of RPC data services. This setup is somewhat similar to data processing in MetaMask except that all our processing is read-only.

Note that our goal is deliver superior user experience to crypto savvy accountants / CPAs and auditors. Therefore, we are providing access to full history about balances for date-hour-timezone of your choosing.

The table below shows the list of protocols-networks that we currently support and the specific sources for corresponding on-chain data.

Use the checkboxes to disable/enable networks specific to your goals. Note that you must select at least one protocol and Ethereum Mainnet is the default in case you disable all protocols. After you finish your changes make sure to reload any other tabs in your browser on ProtocolScout.

Please note that all your edits to settings are saved in local.storage for this machine/browser — no one else can “see” your local settings and our privacy policy is that we don’t record your actions on our servers!

The controls below can be used to accomplish the following actions:

• Reset all settings with the blue button;
• Enable/disable a protocol: toggle the checkbox in the corresponding row;
• Upgrade the data source for coin/token balances, token supply and transactions-by-hash: edit the corresponding row with the pencil icon. Or, to reset back to our public default endpoint use the circular icon in the same row.
• Upgrade the data source for transactions-by-address: follow this link to access setup for all protocols which support transactions-by-address.

There are multiple ways to retrieve historical data from blockchain (nodes). Each approach has tradeoffs. ProtocolScout optimizes retrieval of "balances" amounts and "total supply" amounts for groups of tokens at once. Alternatively, it can retrieve a single token amount in each request. Our default multi-token data retrieval is fast, but it has a cutoff for historical data access.
If you wish to access earlier balances or total supply, please toggle your use to "single token" data retrieval mode: select a specific network and choose an individual token to get its balance or total supply, as of that old(er) date or block. The table below shows cutoff dates for each protocol — the column "MultiTokenCutoff" means that you should submit requests for individual tokens before the date for that protocol.