Blockscout PRO API in Cashboard

Blockscout is a block explorer and indexer. Cashboard calls its API for two jobs: watch-only EVM portfolios, and the followed-wallet swap feed behind Smart money and Smart money graph on Base, Ethereum and Robinhood Chain. Both are read-only lookups of public addresses.

In the Add panel, Portfolio and Net worth sit under Your positions, Smart money sits in Solana, and the Money graph card, which adds a widget titled Smart money graph, sits in Intelligence tools. Both wallet widgets offer Solana, Base, Ethereum and Robinhood; the last three use Blockscout. Token terminal, Networks, the Swap widgets in the Base and Robinhood groups (routed by LI.FI) and the other widgets in the Hyperliquid, Base, Robinhood and Ethereum groups read other sources, and their explorer links only open a page. See the positions, Solana and Intelligence references.

Most chains have a public Blockscout site with an API on its own host, for example https://eth.blockscout.com, and Cashboard uses those hosts by default with no key. Blockscout also offers a hosted gateway, the PRO API, which its documentation describes as one key across 100+ EVM chains on a single host. A PRO key is Blockscout's product. You get it from Blockscout, on Blockscout's terms, and Cashboard Desktop only passes it along with your requests.

The difference matters because a public host can answer a person in a browser and still turn away a program. Blockscout's documentation says its public instances can return HTTP 403 with a challenge page, and recommends the PRO API for programmatic access. Cashboard Desktop and the relay on cashboard.live are programs, not browsers.

When checked on 7 October 2026, a plain request to the public hosts for Base, Arbitrum One, Robinhood Chain, Polygon PoS and Arc was challenged with a 403, the host Cashboard used to list for HyperEVM returned 404 (it lists none now), and the hosts for Ethereum, OP Mainnet, Scroll, ZKsync Era, Gnosis and Linea answered. That is a snapshot. Hosts change their protection without notice.

Find what you want to do in the first column. The network results are the 7 October 2026 snapshot from the coverage table. The Smart money rows apply to Smart money graph too, because both use the same reader and the same saved key.

Cashboard Desktop has a second route for Portfolio on one network. When Blockscout fails for that exact network and you saved a Coinbase RPC connection for it, the widget shows the native balance only, with no price and no tokens, and its source line reads Coinbase RPC. For BNB Chain, Avalanche C-Chain and HyperEVM, which have no built-in Blockscout host, that connection is the only route Cashboard ships, because the PRO gateway serves none of the three. Connections covers it.

The gateway column combines a check made with a key on 1 October 2026 with the supported-chain list Blockscout publishes on its PRO API page, read on 7 October 2026. The two agree on every chain below, and only the list covers Arc. A request to the gateway with no key says nothing about a chain, because it answers 402 for every chain id, so only a key or Blockscout's list can tell. The public-host column comes from a plain program request on 7 October 2026. Blockscout's list is the authority on which chains the gateway supports, and it can change.

The same checks served Celo (42220) and returned 404 for Mantle (5000) and Blast (81457). Cashboard has no portfolio or Smart money network for those three. Which networks a Portfolio widget can read at all is covered in Portfolios and wallets.

Plans, prices and limits are Blockscout's, not Cashboard's, and they change. The table repeats what Blockscout's rate-limits page showed on 7 October 2026. Confirm every figure on Blockscout's site before you rely on it or pay for anything.

Blockscout's documentation adds that a call costs 20 credits by default and some endpoints cost more, that going over your requests per second returns HTTP 429, and that a key which is not sent correctly returns 401. On the Free plan, once the daily credits run out, Blockscout rejects further requests until the daily reset, which its rate-limits page puts at midnight UTC. Paid plans may continue into overage, subject to Blockscout's terms. Keys come from Blockscout's developer portal at dev.blockscout.com, where an account can hold up to 50 of them and the free plan needs no credit card. Cashboard does not read your remaining credits or your plan from Blockscout and shows neither.

Only Cashboard Desktop can store a key. In the API URL field you type the gateway address for one network. Base is 8453, Ethereum is 1 and Robinhood Chain is 4663; the other chain ids are in the coverage table.

https://api.blockscout.com/<chain id>

https://api.blockscout.com/8453
https://api.blockscout.com/1
https://api.blockscout.com/4663

1. 1

   Get a key from Blockscout

   Create an account at dev.blockscout.com and generate an API key. Blockscout's documentation shows keys that begin with proapi_. Treat the key like a password.

2. 2

   Open the Blockscout card

   In Cashboard Desktop open the left panel and choose the Connections tab. The four tabs at the top are icons, and Connections is the fourth, after Add, Boards and Style; its name appears when you hover over it. Find the card named Blockscout. Its badge reads Optional until something is saved.

3. 3

   Fill API URL

   Type https://api.blockscout.com/ followed by the chain id of the network you want Portfolio to read through the gateway. The field is required. The address must use https (plain http is accepted only for localhost and 127.0.0.1) and carry no username or password. A trailing /api/v2 is accepted. If you want the key only for Smart money, you still have to fill this field. Use the network you watch most, because Smart money ignores the URL.

4. 4

   Paste the API key

   The card marks this field optional, but the PRO gateway needs a key, so paste yours. The field is masked. When checked on 7 October 2026, the gateway answered a request with no key at all with HTTP 402.

5. 5

   Choose the Chain

   Pick the network whose chain id is in the URL. The list starts at Base each time the tab opens, never shows the network you saved, and holds all 14 EVM networks Cashboard knows, including some the gateway does not serve. Cashboard attaches the saved URL and key to requests for this one network. If the two disagree, for example a URL ending in /8453 with Ethereum chosen, the Ethereum Portfolio would be answered by Base's endpoint, and Test would not notice.

6. 6

   Save

   Click Save. The card says Saved securely. The value is no longer shown., the API URL and API key fields empty and the badge changes to Connected. Save is disabled when the operating system offers no secure storage.

7. 7

   Test

   Click Test. It checks the saved connection, not what you typed, and it stays disabled until a connection exists. A good result reads Blockscout is reachable for Base., with the name taken from the Chain list. On the gateway address Test also catches a missing or wrong key, because the gateway answers 402 or 401. The next section explains every result.

To change anything, enter all three fields again. A saved value is never shown back, API URL and API key start empty and Chain starts at Base. Save replaces the whole entry, so saving with an empty API key stores a connection without a key. The trash button titled Clear saved credentials appears once an entry is saved and removes it. The card holds one Blockscout entry, so a second network needs the first to be replaced.

Nothing on screen names the route. The source line of Portfolio, Smart money and Smart money graph says Blockscout whether or not a key is saved (Portfolio reads Coinbase RPC after a fallback), and Net worth lists Blockscout among its sources. Test is the way to see what a saved connection answers.

One network for Portfolio, three for Smart money

The connection scopes differ. Portfolio uses the saved URL, Chain and key for one network only. Every other network keeps its public host and never receives the key. Smart money and Smart money graph read only the saved key and send it to https://api.blockscout.com/8453, /1 and /4663 whatever URL and Chain you saved. One saved connection can therefore serve three networks in Smart money and one in Portfolio. If you need Portfolio on two networks that both need the gateway, such as Base and Robinhood Chain, one Blockscout entry cannot serve both.

Clearing the saved connection has the opposite effect, unless the app's environment preconfigures one: Portfolio returns to its public host, and Smart money on Robinhood Chain goes back to Needs a Blockscout key once the app's cached read expires and the widget asks again, within about two minutes.

The web build at cashboard.live cannot store a key. Its Connections tab says Protected provider connections are configured in Cashboard Desktop. and offers a Connection guide link. The hosted site itself uses no Blockscout key as of October 2026, which its status page shows as PUBLIC on the EVM portfolios row, not ENHANCED.

• Portfolio asks a relay on cashboard.live, which asks the public Blockscout host for the network. Your address and network reach cashboard.live as well as Blockscout. Privacy and data covers what leaves your device.
• Smart money and Smart money graph on Base and Ethereum ask the public Blockscout hosts straight from your browser. Nothing passes through cashboard.live. On 7 October 2026 both hosts answered browser requests made from cashboard.live for a test address. A host that refuses a request leaves those wallets unread, and the widget says so.
• Smart money on Robinhood Chain shows Needs a Blockscout key once you follow a wallet, and makes no request. The message points you to Connections, which cannot hold a key on the web, so this network cannot work there. Use Cashboard Desktop.

Cashboard asks Blockscout plainly and does not manage load for you. These are the numbers that matter when you size a plan.

The Smart money rows above describe the Smart money widget, which asks every 120 seconds. Smart money graph uses the same reader and saved key, but follows up to 10 wallets and asks every 60 seconds. Widgets with the same network and the same wallet addresses share one read. While B Cash watches a board, it can also request wallet feeds outside widget rendering, roughly every 30 seconds while Cashboard runs, for up to 3 wallet widgets per watched board, and it reuses a matching read from the last minute when one exists. Include those watches when you size a plan. Public builds label Agent Coming soon and run no monitor, so they make none of these requests.

When Blockscout refuses or runs out

A failure on every wallet in a Smart money round, such as a 401, 403 or 429, does not show an error. The widget shows the empty state No recent swaps, and the i note adds N wallet(s) could not be read this round. If only some wallets fail, the others still show. Wallet swaps are temporarily unavailable, with Blockscout did not answer. Public instances rate-limit heavy reads; try again in a minute., appears only when the whole request fails and nothing is on screen.

Smart money graph says it in its own words. Wallets it could not read add the amber line History unavailable for <names>. The graph is incomplete., and when none could be read the list reads No readable swaps yet. A failed request with nothing on screen shows Wallet history is unavailable. On Robinhood Chain without a key the graph shows the notice Robinhood Chain is read through the Blockscout Pro API. Add a Blockscout key under Connections to follow wallets there. as an amber line above No recent swaps detected, and not the Needs a Blockscout key title.

In Portfolio, a failed read with nothing on screen shows Portfolio data is temporarily unavailable and Your address and local portfolio are still saved. With an earlier reading on screen, an amber bar reads Refresh failed · showing the reading from <age> ago. None of these widgets shows the HTTP status. Test is the place to see one.

• Cashboard Desktop saves the URL, key and chain as one entry, encrypted with the operating system's secure storage, in a file in the app's data folder. If the system has no secure storage, or only a plain-text fallback, Cashboard refuses to save and never writes the key in plain text.
• The key is never shown again. The fields empty after Save, and the app window learns only whether a connection exists and whether you saved it or an administrator preconfigured it. The value does not go back to the window or to any widget. It passes once from the masked field to the app's main process when you click Save.
• Cashboard's own code does not write the key to a log, and its own error messages carry only the HTTP status, such as Blockscout returned 401.
• The key is not part of any board, so share links and board exports do not carry it. The wallets you follow are different: Smart money and Smart money graph save them, and Portfolio saves its address, with the board. Share links remove them, and Export this board keeps them. Templates and sharing covers what a share link carries.
• The web build holds no key: none can be entered there, and the hosted site uses none.
• The card's own reminder applies: Only provider credentials belong here. Never enter a seed phrase, wallet private key, or exchange trading secret.

Where the key is sent

The Portfolio, Smart money and Smart money graph requests also carry the public address you watch or follow, because that is what is being looked up. On desktop the requests go from your computer straight to Blockscout. Cashboard's servers are not involved.

For problems outside Blockscout, see Troubleshooting. Keys for the other providers are on Connections.