Risk and flows widgets

Use the Risk and flows group in the Add panel to check leverage, forced liquidations, stablecoin pegs, money flows, prediction market odds and network health, plus your own Dune queries and MCP tools on desktop. Unfold it to find nine cards. A card label is not always the widget's name, so the table below maps one to the other.

Controls in a widget header respond once the widget is active. Click a widget to select it and click again to use it (a selected widget shows a Click to use this widget pill); a widget you have just added starts active. Every widget here names its source under its title, shows its freshness in a pill on the right of its header, and has an info button (an i icon) beside the pill that opens a short methodology note. A new Perps risk widget is titled Perps risk terminal, and any title can be changed in the Style tab.

Every flag, colour band and alarm level in this group is a fixed value inside Cashboard. No setting changes them, they are the same on every board, and none is tuned to your holdings or risk tolerance. Treat a flag as a prompt to look closer. Nothing in these widgets is trading advice.

How the widgets pair

• Leverage: Perps risk shows where open interest and funding sit across four venues, Liquidations shows positions being closed by force as it happens, and Perps positions shows how far your own Hyperliquid positions are from liquidation. Funding rates ranks funding across Hyperliquid markets. The Pressure figure in Perps risk is not liquidation data.
• Dollar liquidity: Stablecoin risk and Market flows both read DefiLlama's stablecoin data, so a depeg flag in one lines up with a supply move in the other. Market flows takes its total from the daily supply series and Stablecoin risk sums the per-coin list, so the two totals can differ by a fraction of a percent. Chain status tells you whether the network you settle on is keeping up.
• Sentiment: Prediction markets puts prices on events such as rate decisions and elections, next to your price and stock widgets.
• Research: Dune query brings in one query of your choice. It runs in the desktop app only.

Some data this group points at is not available, and Cashboard says so on screen instead of estimating. As of October 2026:

The Data sources page lists every provider and how each is reached. Keys for the desktop app are explained in Connections.

Compares four perpetual futures venues side by side on 24 hour volume, open interest and a positioning ratio, and shows how far their funding rates for BTC, ETH and SOL disagree. Use it to see where leverage sits and where funding differs between venues. It does not measure liquidations.

What it shows

• Four venue cards, always in this order whatever the filter says: Hyperliquid, Lighter, Aster and Jupiter Perpetuals. Each shows a status chip (Live, Limited or Unavailable), 24 hour volume with its share of the four-venue total (<n>% of volume), OI (open interest in dollars), the market count (<n> mkts) and Pressure.
• Pressure is open interest divided by 24 hour volume, to two decimals: green below 0.8, amber from 0.8, red from 1.5, and n/a when the venue publishes no open interest. When a venue is not Live, the reason appears under its card and in its tooltip.
• Beside the filter, <total> 24h across <n> venues. The count includes Limited venues and leaves out only Unavailable ones.
• One panel per asset, titled BTC funding spread, ETH funding spread or SOL funding spread: the gap between the highest and the lowest venue rate as a percentage per hour with four decimals, then /h, the same gap annualised (% APR) and the number of reporting venues.
• In each panel, one bar per reporting venue, centred on zero: green to the right for a positive rate, red to the left for a negative one, labelled with the venue's annualised rate. All panels on screen share one scale.

How to use it

• Choose All, BTC, ETH or SOL in the control at the left of the header to pick which funding panels are drawn. The venue cards stay.
• Press the refresh icon to read all four venues now. Otherwise the widget reloads every 30 seconds.
• Hover a venue card to read why that venue is Limited or Unavailable.

Settings

Data and refresh

• The public APIs of Hyperliquid, Lighter, Aster and Jupiter Perpetuals, requested in parallel with a 10 second timeout each. A venue that fails shows as Unavailable with the failure text as its reason, and the other cards stay.
• Hyperliquid supplies volume, open interest and funding, read as a one hour rate. Lighter supplies volume, open interest (markets with a mark price only) and funding, which Cashboard treats as an eight hour rate. Aster supplies volume and funding, with the interval read per symbol and eight hours as the fallback, but no open interest. Jupiter Perpetuals supplies volume for SOL, BTC and ETH only.
• Reloads every 30 seconds. On desktop the app shares one result for 30 seconds. On the web, the Aster requests go through Cashboard's relay on cashboard.live and the other venues are called straight from your browser.

Good to know

• Pressure is a positioning-per-turnover proxy, not liquidation data. A high number means a lot of open interest compared with the day's trading, not that positions are close to liquidation. Use Liquidations to see forced closes.
• Only Hyperliquid and Lighter publish open interest here, so Pressure exists for two venues. Aster and Jupiter Perpetuals are always Limited, by design and not because of an outage.
• The % of volume shares mix definitions: Hyperliquid reports notional volume, Lighter and Aster report quote-token volume, and Jupiter its own volume figure. Read the shares as indicative.
• Only BTC, ETH and SOL are compared. Annualised figures are the hourly rate times 24 times 365, without compounding. A panel where no venue reports a rate reads n/a /h · n/a APR · 0 venues and has no bars. By the usual convention a positive rate means longs pay shorts.

Pairs well with Liquidations, Funding rates, Perps positions, Hyperliquid markets. See the Perps risk widget page for a ready-made board.

A live tape of forced liquidations on Binance, Bybit and OKX, with long and short totals, a histogram of the recent window, a cascade alarm and a per-coin ranking. Use it to see when leveraged positions are being closed by force and which side is getting hurt.

What it shows

• A summary block: Longs rekt <
  gt; on the left, <
  gt; shorts rekt on the right and last <n> min · <count> prints between them (<k> of <n> min seen while the page has listened for less than the window). A split bar shows the long share of liquidated dollars in rose and the short share in green.
• A 30-bucket histogram of the window: longs above the centre line, shorts below, newest bucket darker. Hover a bucket for Longs $X · shorts $Y.
• A heat card for the last 60 seconds only: Calm, Heating up from $250,000 or Liquidation cascade from $1,000,000, with <
  gt; in the last 60 seconds. A Largest card names the biggest single liquidation in the window.
• Header indicators for Binance, Bybit and OKX (green streaming, amber connecting, red unreachable and retrying) and a badge that reads Live when at least one stream is up and Reconnecting otherwise.
• Tape view, the default: up to 80 rows, newest first, with age, venue chip, symbol, a Long or Short chip, price and a size bar with the dollar amount. Sizes turn bold from $100,000, and $1,000,000 and above get a flame and an amber ring.
• Coins view: the top 30 coins in the window by dollars liquidated, each with rank, total, a long and short bar and a print count such as 12×.

How to use it

• Pick 5m, 15m or 1h to set how far back the totals, histogram, Largest card, tape and Coins list look. The heat card ignores it.
• Switch between Tape and Coins.
• In Tape view choose All, $10K+ or $100K+ to hide smaller prints from the list. Totals, histogram, heat card and Coins still count every print.
• Hover a venue indicator for its status. Bybit's tooltip also says how many perpetuals it follows, and OKX's says when contract sizes are not loaded yet.

Settings

Data and refresh

• Three public WebSockets opened from your own device, with no relay, key or account: Binance's USD-M futures stream, OKX's swap channel and Bybit's per-contract topics. Bybit has no market-wide topic, so the widget follows the 60 USDT perpetuals with the highest 24 hour turnover, or a fixed list of 20 majors when Bybit's ticker list cannot be read.
• OKX sizes arrive in contracts. Cashboard converts them to dollars with OKX's own contract sizes and skips contracts missing from that list. Those sizes and the Bybit list are fetched once an hour, by the app's main process on desktop and by the browser on the web.
• Long means a long position was force-sold and Short that a short was force-bought. Size is price times quantity.
• Sockets are shared by every Liquidations widget on the page and reconnect with a delay that grows from 1 to 30 seconds. The buffer keeps the last hour, at most 8,000 prints, in memory only.

Good to know

• Totals are a floor, not an estimate. Binance and OKX publish at most one liquidation per contract per second, Bybit is limited to its busiest 60 USDT perpetuals, OKX contracts without a known size are skipped, and on-chain venues such as Hyperliquid are not included.
• History starts when the page starts listening and covers at most one hour. Nothing is stored, so closing the tab or the app drops it, and the widget collects only while it is on screen. The tape follows the window setting too: a print older than the window leaves the list. A second Liquidations widget on the same page starts with the prints already received.
• Empty states: Nothing liquidated at this size yet with Prints appear the moment an exchange force-closes a position. when a stream is live; Connecting to the exchanges with Binance, Bybit and OKX stream liquidations to anyone outside the US. when none is; No liquidations in this window yet in Coins view; Waiting for the first liquidation… in the Largest card.
• There is no refresh button and no error card. A blocked or failing stream shows as a red dot and the Reconnecting badge.

Pairs well with Perps risk, Funding rates, Hyperliquid markets, Prices. See the Liquidations widget page for a ready-made board.

A risk table for the largest US dollar stablecoins: price against the $1 peg (yield-bearing assets carry a NAV tag instead), supply and share, supply change, the best single-asset yield, where the supply sits and a Low, Watch or High flag. Use it to notice a depeg or a sharp drop in supply.

What it shows

• In the header, a pill that reads All pegs healthy or <n> flagged: <SYM>, <SYM>, <SYM> (the first three flagged symbols; Watch and High both count, and only visible rows are counted), and Supply <total>, the total of every tracked asset.
• Asset (logo, symbol, name) and Price · peg: the price to four decimals, the signed distance from $1 to three decimals and a gauge spanning 1% either side of $1. The marker is green under 0.5% away, amber from 0.5% and red from 2%. It reads n/a without a price.
• A yield-bearing asset, one DefiLlama flags because its price rises as it accrues yield (tokenized treasury funds such as USYC and USDY), shows its price with a NAV tag and accrues yield instead of the distance and the gauge. Its Risk chip says on hover that it is rated on supply changes only.
• Supply · share: circulating supply in dollars, its share of all tracked supply and a bar. 1d: the one day supply change, with the seven day change beneath as 7d (hover for 7d and 30d).
• Yield: the APY of the largest single-asset stablecoin pool for that ticker outside credit projects, with the project name beneath (hover for project and chain). It reads n/a when no pool lists the ticker, a pulsing bar while the pool list loads, and slow or error when it could not be read, with a notice above the table. A credit pool appears only when the ticker has no lending pool of a fair size, and then the project name is followed by · credit. Top chains: the first two chains by supply and a bar of the top four.
• Risk: a chip that reads Low, Watch or High.

How to use it

• Choose the row count in the header: Top 5, 10, 15 or 25. A value saved by a template or board, such as 12, is added to the list.
• Press the refresh icon to read DefiLlama now.
• Hover the peg gauge for the exact price and deviation, and the chain bar for each chain's percentage.

Settings

Data and refresh

• DefiLlama only, in two separate reads. The stablecoin list with prices has a 10 second timeout and fails into the widget's error card. The yield pool list, an 11 MB file, has a 20 second timeout and is read on its own, so the table appears without waiting for it and the rates fill in when it arrives. If that read times out the Yield cells show slow, if it fails they show error, and a notice names the problem. Rates from an earlier good read stay on screen under that notice.
• Only assets with a US dollar supply figure are listed (as of October 2026 that leaves out coins pegged to the euro, pound, yen and other currencies, and variable-peg assets). Rows are sorted by supply, largest first, then cut to the row limit. Share and the header total use all listed assets, not only the visible rows.
• Supply change compares circulating supply with DefiLlama's figures for one day, one week and one month earlier. Deviation is the price minus $1, in percent, for dollar-pegged assets that have a price and are not yield-bearing. Yield is the pool with the greatest TVL among stablecoin pools with single-asset exposure whose ticker equals the asset's, skipping credit projects. Credit projects are the ones DefiLlama lists as uncollateralized lending plus Maple, whose Syrup pools fund institutional loans. The list is kept by hand, so a new credit project shows without the mark until it is added. A lending pool replaces a larger credit pool only if it holds at least a tenth as much TVL.
• The supply list reloads every 5 minutes and the pool list every 30 minutes, or after 2 minutes following a failed read. DefiLlama serves the supply list from a cache of about 30 minutes, and the file itself can be older. The header pill shows its own timestamp as data <age> ago, taken from the Last-Modified header, or may lag 30m+ when there is none. On desktop the app shares the supply list for 60 seconds per row limit and the pool list for 15 minutes, and a failed pool read for 1 minute. On the web the browser calls DefiLlama directly, with no shared cache.

Good to know

• The risk rules are fixed. High: the price is 2% or more from $1, or supply is down 20% in a day, 30% in a week or 50% in a month. Watch: the price is 0.5% or more from $1, or supply is down 5%, 10% or 20% over the same periods, or a dollar-pegged asset that is not yield-bearing has no price at all. Everything else is Low.
• Yield-bearing assets are not compared with $1. They are built to trade above it: on 10 October 2026 DefiLlama priced USYC at 1.1397 and USDY at 1.1487. For an asset DefiLlama flags as yield-bearing, the widget shows no distance, skips the missing-price rule and rates it on supply drops alone, so a run on it still turns the chip Watch or High. A fall of its price is not checked, so read the price beside the tag. As of October 2026 DefiLlama also flags YLDS, whose price sits near $1, and a few small assets this way.
• The deviation text is grey under 0.05% and red above, in either direction. The price is DefiLlama's, not Cashboard's own market price, so it can differ from an exchange quote. The yield match is by ticker text only, so two assets that share a ticker show the same yield.
• Empty and error states: No stablecoin rows returned with The source responded successfully but has no assets to show., and Stablecoin monitor is temporarily unavailable with a Try again button. A widget that already has data keeps showing it when a refresh fails.

Pairs well with Market flows, Chain status. See the Stablecoin risk widget page for a ready-made board.

Stablecoin supply, DEX trading volume and the capital sitting on Ethereum layer 2s in one view: how much dollar stablecoin exists and how it moved over 1, 7 and 30 days, which chains hold it, which venues trade the most, and how much value layer 2s secure, split into canonical, native and external. Bridge volume and ETF flows have no free source, so they have no tab.

What it shows

• The header: tabs Overview, DEX and L2 capital, then Stables <total> <±x.xx% 7d>, or Liquidity entering and leaving crypto before data arrives.
• Overview, stablecoin tile: Stablecoin supply as a total with two decimals, a 30 day sparkline, chips 1d, 7d and 30d with signed percentages, and the source line DefiLlama · latest snapshot, <Mon d> UTC. The total is the latest snapshot of DefiLlama's daily series, not a daily close, and the chips and the sparkline read that same series. If the series cannot be read, the tile sums the coin list instead, reads DefiLlama · sum of <n> coins, no change data and shows n/a in the chips.
• Overview, two more tiles: DEX volume · 24h with 1d and 7d changes and Top: <protocol>, and L2 capital · TVS with the total value secured on layer 2s, 1d and 7d changes and Top: <chain>.
• Where stablecoins sit (share of chain-tracked supply): up to six chains with bar, dollars and share. Busiest DEXs (24h spot volume): the top five protocols with chains, volume, <x.x>% share and 1d change. Biggest layer 2s (value secured, 7d change): the four layer 2s with the most value.
• DEX tab: the total (DEX spot volume, 24h) with 1d and 7d, then Volume by chain and Top venues, up to eight rows each.
• L2 capital tab: the total with two decimals beside Value secured on layer 2s, chips 1d, 7d and 30d, a line reading Latest snapshot <Mon d, hh:mm> UTC (amber and reading Stale: last L2BEAT reading ... once it is more than 24 hours old) and a sparkline. Where the value came from (share of total · 7d change): a stacked bar and three rows, Canonical, Native and External, each with dollars, share and seven day change. Activity (all tracked chains): Transactions · <day>, UOPS · <day> and Transactions · 7d average with a vs prior 7d chip and a 30 day sparkline. Biggest layer 2s (value secured · <n> layer 2s): up to ten rows with rank, logo, name, category, stage, an Under review flag where L2BEAT sets one, dollars, <n>% of L2s and the seven day change.

How to use it

• Click a tab to switch section. The choice is saved with the board.
• Press the refresh icon to read DefiLlama and L2BEAT now.
• Open the i button in the header for the definitions of supply, DEX volume and value secured. On the L2 capital tab the header pill shows the age of L2BEAT's own reading, not of your last refresh.

Settings

Data and refresh

• DefiLlama for stablecoins and DEX volume, L2BEAT for layer 2 capital. Each refresh makes up to six requests in parallel, each with its own timeout (10 seconds for DefiLlama, 12 for L2BEAT): DefiLlama's daily stablecoin supply chart, supply by chain and the DEX volume overview, and L2BEAT's value secured, project list and daily activity. If the supply chart fails, one more request reads the coin list as a fallback. Each part fails on its own, so a failed part shows a short notice and the rest still loads.
• Stablecoin total: DefiLlama's daily total for US dollar stablecoins. Its newest point is the latest snapshot of the current day, not a daily close. The 1d, 7d and 30d changes compare that point with the point stamped exactly 1, 7 and 30 days earlier, and read n/a when that day is missing. The headline, the changes and the sparkline come from this one series, so they agree. Stablecoin risk sums the per-coin list instead, so its supply total can differ from this one by a fraction of a percent.
• Chain split: DefiLlama's stablecoins by chain. Shares are of that feed's own total over every chain it lists, which differs a little from the headline because the two feeds count differently.
• DEX volume counts spot DEXs only: DefiLlama's Dexs category, without venues booked entirely off chain. DefiLlama's overview also lists prediction markets and launchpads, which are filtered out. 1d compares with the previous 24 hours and 7d with the same day a week earlier.
• L2 capital: the l2beat.com website API (tvs, summary and activity under /api/scaling), which is free, needs no key and has no published contract, so Cashboard reads it defensively and skips any row it cannot parse. Total value secured (TVS) is the sum of canonical, native and external value across layer 2s. The 1d, 7d and 30d changes compare the latest snapshot with the reading nearest that many days earlier. Readings are 3 to 6 hours apart and the series currently covers about 30 days, so a window it does not reach reads n/a. A chain's seven day change is L2BEAT's own figure. Layer 3 chains such as Hyperliquid are not part of L2BEAT's layer 2 total, so they are not listed. Transactions and UOPS (user operations) are L2BEAT's daily counts across the chains it tracks, for the last full UTC day; a day still in progress is left out.
• Bridges: 402: DefiLlama bridges are paid. DefiLlama answers HTTP 402 for bridge volume because it serves it only on its paid API plan, no key can be entered for it, and Cashboard no longer requests it. ETF flows: there is no source.
• Reloads every 5 minutes. On desktop the app shares a result for 60 seconds. On the web every request goes straight from your browser to the provider.

Good to know

• On the L2 capital tab a chain's share is of the combined value of every layer 2 in L2BEAT's project list, which can sit a fraction of a percent apart from the headline because the two are read at slightly different moments. An Under review flag is L2BEAT's, and that chain's value is still counted.
• Value secured is not bridge volume and not a count of users. It is the dollar value of the assets held on a layer 2 at the snapshot. Canonical value came over the chain's own bridge, external value over a third-party bridge, and native value was issued on the layer 2 itself.
• Partial states: Chain split is temporarily unavailable., DEX volume is temporarily unavailable., Activity is temporarily unavailable., The canonical, native and external split is temporarily unavailable., The chain list is temporarily unavailable. and Public feed unavailable on the tiles. If L2BEAT cannot be read at all, the tab says L2 capital is temporarily unavailable. Try refreshing in a moment. If nothing loads the widget shows Flows are temporarily unavailable with a Try again button.
• Overview shows the top six of the eight chains read for the stablecoin split. An n/a marks any figure that could not be read; Cashboard does not estimate.

Pairs well with Stablecoin risk, Chain status, Chain pulse, L2 scoreboard. See the Market flows widget page for a ready-made board.

Live odds from Polymarket and Kalshi in one list, or the largest recent Polymarket bets. Each market row shows the leading outcome's probability, its venue, volume and time to resolution.

What it shows

• Markets view, one row per market: an avatar, the event title in grey when it differs from the question, the question, the leading outcome's probability as a large percentage with its name beneath, and a bar.
• Under the question: a venue pill (Polymarket or Kalshi), a chip ▲ N pts 24h or ▼ N pts 24h when the move is at least 0.5 points and the venue reports one, and up to two more outcomes as <name> <pct>%.
• At the right: Vol $X (Polymarket, dollars) or Vol N ct (Kalshi, contracts), · Liq $X when known, and the time left: ends in 5h, ends in 12d, ends Mar 2027 or ending.
• Whales view: <n> bets of $10K+ · <total> in total, then one row per bet with the market title, Bought <outcome> or Sold <outcome>, the price as at 62¢, its age (42s ago), the trader's name when there is one, a size bar and the amount with the caption bet or sold. Bets under 5 minutes old get a pulsing green dot, and $100,000 or more a flame and an amber tint.

How to use it

• Switch between Markets and Whales.
• In Markets view pick a category: No sports, Crypto, Macro, Politics, Sports or All. If a category leaves few rows, raise the row limit, because the filter works on a pool three times the limit.
• Choose Top 5, Top 10, Top 15 or Top 20 in the row limit select, which appears only while the widget is active. It also caps the Whales list.
• Press the refresh icon to reload the current view.
• Hover a row and click its link icon to open the market page: in a new Web app widget on the same board on desktop, in a new browser tab on the web.

Settings

Data and refresh

• Polymarket (public Gamma API): active events by 24 hour volume, one row per event using its highest-volume active market, so one football game or one Fed meeting is one row. Kalshi: open markets without multivariate combinations, ordered by 24 hour volume within the page Kalshi returns, so several strikes of one event can appear.
• The two lists are interleaved one for one, starting with Polymarket, into a pool of three times the row limit (at most 60). The category filter is then applied and the result is cut to the row limit. It is not one global ranking, since Polymarket volume is in dollars and Kalshi volume in contracts.
• Probabilities are Polymarket's outcome prices; for Kalshi, Yes is the midpoint of the best bid and ask when both exist (otherwise the last price, bid or ask) and No is 1 minus Yes. Categories come from Polymarket event tags and from words in Kalshi tickers, the first match winning in the order sports, crypto, macro, politics. Anything unmatched is other and shows under All and No sports only.
• Whales: Polymarket's public data API, the latest 50 trades of $10,000 or more, newest first. Polymarket can delay a bet by up to five minutes. Names are Polymarket pseudonyms or names the trader chose; wallet-like names are dropped.
• Markets reload every 30 seconds and whales every 60, and only the visible view loads. On desktop the app shares results for 30 seconds. On the web, Kalshi requests of up to 100 markets go through Cashboard's relay and Polymarket is called from your browser. If one venue fails the other still shows.

Good to know

• Probabilities are market prices, not forecasts. The 24h chip is Polymarket's move for the first listed outcome, usually Yes; when the leading outcome is the other side, the arrow describes the opposite side. Kalshi rows never carry it.
• Whales covers the latest 50 trades only and shows up to the row limit, so it is not every bet. Kalshi volume stays in contracts, so Vol N ct and Vol $X cannot be compared directly.
• Empty states: Nothing in <category> right now with <n> active markets were filtered out. Switch the category to see them. (with the default category it reads Nothing in no sports right now), and No active markets returned with a Refresh markets link. Whales: No bets of $10,000 or more lately.
• Errors with nothing loaded: Prediction markets are temporarily unavailable and Polymarket bets are temporarily unavailable, each with a Try again button. The source line reads Polymarket + Kalshi or Polymarket data API, and the pill reads Waiting for live data until the first market reading.

Pairs well with Stocks, Tokenized stocks, Paper trading. See the Prediction markets widget page for a ready-made board.

Checks the public RPC endpoint of up to 15 networks and shows, for each, how old the newest block is, the current fee, the block height and how long the check took. Use it to see whether a chain, or the public node you depend on, is falling behind.

What it shows

• A chip at the top left, <n>/<total> live, green when every row is Live and amber otherwise, then fastest RPC <Chain> · <ms> ms.
• One row per network: the logo with a health dot, the name and RPC <ms> ms (green under 300 ms, amber under 1,000 ms, red from 1,000 ms), then Fee, Block and a status chip with <n>s ago.
• Fee: gwei on EVM networks (three decimals, two significant digits below 0.01) and µL/CU on Solana with a k suffix from 1,000; n/a when the node gives no figure. A small trend line appears after three readings.
• Block: the height in compact form such as 12.3M or 1.2B, with the full number on hover. The status chip reads Live, Lagging, Stalled or No age, with age n/a when the block time is unknown.
• The source line reads Public RPC, and the pill shows the age of the newest block read. It reads Source down when every network failed.

How to use it

• Make the widget active to reveal a chip row of all 15 networks: Ethereum, Base, Solana, Arbitrum One, Robinhood Chain, Arc, HyperEVM, BNB Chain, Polygon PoS, OP Mainnet, Avalanche C-Chain, Linea, Scroll, ZKsync Era and Gnosis. Click a chip to add or remove a network. At least one must stay selected.
• Rows keep the order in which you added the networks.
• Press the refresh icon to recheck every network now, or the retry icon on a failed row to recheck that one.

Settings

Data and refresh

• One public RPC endpoint per network, the first one Cashboard lists for it, with no key: Ethereum and Solana through PublicNode, Base at mainnet.base.org, Arbitrum One at arb1.arbitrum.io, Robinhood Chain at rpc.mainnet.chain.robinhood.com, Arc at rpc.mainnet.arc.io, HyperEVM at rpc.hyperliquid.xyz, BNB Chain at bsc-dataseed.bnbchain.org, Polygon PoS at polygon.drpc.org, OP Mainnet at mainnet.optimism.io, Avalanche C-Chain at api.avax.network, Linea at rpc.linea.build, Scroll at rpc.scroll.io, ZKsync Era at mainnet.era.zksync.io and Gnosis at rpc.gnosischain.com.
• On EVM networks the chain id (checked against the expected one), the gas price (eth_gasPrice) and the latest block number are requested at once, then that block is fetched to read its timestamp. On Solana the slot, block height and recent prioritization fees are requested at once, then the block time of that slot. Each call times out after 10 seconds.
• Block age is the time Cashboard received the reading minus the block's own timestamp, in whole seconds, on your device's clock. RPC ms is the elapsed time of the whole read, from the first request until the block timestamp is back. It is not a ping: three requests run in parallel and a fourth follows, so it covers at least two round trips plus the node's work, measured from your device.
• Fee: on EVM networks the node's suggested gas price in gwei; on Solana the median of the node's recent prioritization fees in micro-lamports per compute unit.
• Each network refreshes every 15 seconds, with two retries. On desktop the app shares a result for 15 seconds per network. On the web the browser calls the endpoints directly.

Good to know

• Health is decided by block age alone. On Solana a block is Live under 5 seconds old, Lagging under 30 and Stalled beyond. Ethereum uses 30 and 120 seconds. Every other EVM network uses 15 and 90 seconds. No age appears when the node gives no block time.
• Lagging or Stalled can mean the chain is slow or that the one public node you are reading is behind. The widget cannot tell the two apart. A clock that is several seconds off on your device moves every age by the same amount.
• The EVM fee is the node's suggested gas price, which can differ from the protocol's base fee. The trend line holds the last 24 readings since the widget appeared on screen (about six minutes), is not saved, and is green when the latest value is at or below the first.
• A failed row reads RPC temporarily unavailable with a retry button, and an endpoint that reports a different chain id than expected fails the same way. A new widget is titled Chain status, although its Add panel card is Networks.

Pairs well with Stablecoin risk, Market flows, Chain pulse. See the Chain status widget page for a ready-made board.

Draws up to six chains as live heartbeat lines, one beat for each new block: Ethereum about every 12 seconds, Hyperliquid about 14 times a second, and Solana, Arbitrum One, Base and Robinhood Chain in between. Use it to see how each chain is ticking and to notice when one goes quiet. It shows the rhythm as it reaches your browser, not an official block time.

What it shows

• One strip per chain, in the order you chose. On the left: the chain's logo and name with a status dot, its rhythm (14 blocks/s or 1 block per 12 s, in slots on Solana) and the age of its latest block (last block 2.4 s ago). On the right: a line that scrolls left over the last 20 seconds, flat between beats, with a heartbeat-shaped spike at each new block.
• Spike height. On Ethereum and Base it is how full the block is: gas used over the gas limit, from 15% to 100%. Base blocks use a small share of a large limit, so its spikes mostly sit at the 15% floor. On Arbitrum One, Robinhood Chain and Hyperliquid it is the block's gas used (its transaction count on Hyperliquid) against the 95th percentile of the last 240 blocks, and until 8 blocks have been seen the spikes are drawn at half height. Solana spikes are all the same height, and a small notch under the line marks a slot number the node never announced.
• The header: <n>/<total> live, green when every line is live and amber otherwise; a red <n> flat chip while any line is flat; last 20 s, the width of the trace; and the Sound button.
• Status words under each name: connecting, waiting for the first block, last block <age>, offline - retrying, and in red no block for <n> s (no slot on Solana).
• Hover a strip to read its latest block: the number, how full it is or how much gas it used and, on Hyperliquid, the transaction count and the proposer's address.
• When no chain can be reached, one message reads Cannot reach any node from this network, with a Refresh link.

How to use it

• While the widget is active, click a chain's chip to add or remove its strip. At least two chains stay. A chain you add goes last.
• Click Sound for a quiet tick on each block, pitched differently for each chain and limited to eight a second per chain. Click it again to turn it off.
• Click Refresh in the unreachable message to reopen the connections at once.
• With your system's reduced motion setting on, the lines stop scrolling: each beat is a still tick mark, and the picture refreshes once a second.

Settings

Data and refresh

• Each chain's own public WebSocket feed, opened from your browser or app with no key: Ethereum, Arbitrum One, Base, Robinhood Chain and Solana through PublicNode, and Hyperliquid at rpc.hyperliquid.xyz. The EVM chains send each new block header, Solana each new slot, and Hyperliquid each block with its transaction count and proposer.
• A beat is stamped with the time it reached your device, not with the chain's own block time, so the rhythm includes your network and the node. Lines are drawn only while the widget is on screen and the page is showing. After 60 seconds in a hidden tab the connections close, and they reopen when you return, with the lines starting empty again.
• A dropped connection retries after 1 second, then waits twice as long each time up to 30 seconds. Hyperliquid is pinged every 20 seconds to keep its connection open. Two heartbeat widgets on one board share the same connections.

Good to know

• A line turns red when nothing arrives for three times the usual gap between its beats, and never sooner than 3 seconds. Until enough beats have arrived to measure that gap, Ethereum waits 36 seconds and the other chains 3. Red can mean the chain, the public node or your own connection, and the widget cannot tell them apart. A failed connection reads offline - retrying instead.
• The rhythm figure averages the last 10 seconds of arrivals, so it can read high or low just after a burst of blocks.
• Arbitrum One and Robinhood Chain report a gas limit of 2^50, which says nothing about how full a block is, so their spikes compare each block with the recent ones instead.
• After a reconnect, Solana slots are not compared with the ones from before, so a reconnect never shows as skipped slots. On Hyperliquid the blocks the node replays on connecting only set the scale; the newest one is the beat.
• This is not a status page. For block age and fee per network, use Chain status.

Pairs well with Chain status, Chain pulse, Ethereum pulse.

Shows the latest saved result of a Dune query as a table, a line chart or a bar chart, read with your own Dune API key. Use it to keep a query from dune.com next to the rest of your board. It reads saved results and never runs the query.

What it shows

• The header: a query button with the query's title, or Query <id>, that opens the picker (tooltip Choose a query); a summary such as 100 rows · updated 3h ago or 100 of 4,200 rows · updated 3h ago; the view switch Auto, Table, Line, Bar; a link icon that adds the query's dune.com page to the board as a Web app widget; and a refresh icon.
• The query picker, shown when no query is set or when you click the query button: a Query ID or link field with a Show button, a Presets list (Public queries) and Rows to read.
• Table: every column and row that was read, with a sticky header and Dune's column order. Numbers are compact with the exact value on hover, times are UTC, and empty cells read n/a.
• Line: numbers over time, up to four series, with a hover tooltip, a legend for two or more series and an axis that starts at zero when the data allows it. Bar: one number per label, at most 25 bars, captioned <value> by <label>.
• Without a key, a card titled Connect your Dune API key with the steps and the buttons Get an API key and Check again. The source line reads Dune and the pill read <age> ago.

How to use it

• Create an API key at dune.com/settings/api.
• On desktop open Connections (the plug icon at the top of the tool panel; Ctrl \ or Cmd \ shows the panel when it is hidden), paste the key into API key under Dune and press Save. Dune widgets on screen reload at once.
• Press Test to check the key. It reads one row of a public query, spends credits for that row and answers Dune accepted the API key. The trash icon (Clear saved credentials) removes a saved key.
• Pick a preset, or type a query number (3213428 or #3213428) or a link such as dune.com/queries/3213428/5387463 into Query ID or link and press Show. A dashboard link is refused, because a dashboard holds several queries.
• Choose Rows to read: 25, 100, 250 or 1,000. More rows cost more credits and trigger a new read.
• Pick Auto, Table, Line or Bar. A view the current columns cannot support is disabled, and its tooltip says what it needs, for example Needs a date column, a number column and at least two dates.

Settings

Data and refresh

• Dune's API: the latest cached result of the query, with the key sent only in a request header to api.dune.com and never in a URL. Cashboard never starts a run. Dune bills each read in credits by the size of the result, so Cashboard asks only for the rows you chose; Cashboard does not state the credit cost of a read, so check your Dune plan.
• On desktop each query and row setting is shared for 5 minutes, so the refresh button within that time returns the read you already have and the pill's read time stays old. The widget rereads on its own every 15 minutes, but only after a successful read. A request times out after 20 seconds and is retried at most once, never for a rejected key, a missing cached result or a rate limit.
• updated <age> ago is when Dune last finished running the query (the UTC time shows on hover). The pill's read <age> ago is when Cashboard last received the result. All dates and times in the widget are UTC.
• The web build makes no Dune request at all.

Good to know

• The widget is as fresh as Dune's last run of the query. To get newer data, run the query on dune.com. Cashboard cannot run it, pass parameters, sort or filter, and it reads single queries, not dashboards.
• Errors: Dune rejected your API key (wrong, revoked or expired); No cached result yet (Dune answers the same way for a private or deleted query, so the widget cannot tell them apart); Dune is rate limiting your key; and This Dune query could not be read with Dune's reason, such as Dune is still running this query. Try again in a minute. or Dune took too long to answer. Try again in a minute.
• A refresh that fails while rows are on screen shows Refresh failed · showing the read from <age> in an amber bar. The widget dims to 60% while a new row limit loads. An empty result reads The latest run returned no rows.
• Auto picks Line when there is a date column with numbers and the date is the first column or the rows run in date order, Bar for exactly one text column and one number column with at most 25 rows, and Table otherwise.
• Line needs at least two dates. When rows repeat a date for several categories it draws one line per category from the first number column, the four largest by total size, with +N more <column> values for the rest; the first value for a date wins and nothing is summed. Otherwise each number column is a line, up to four, and a column more than 20 times larger or smaller than the first is left out (+N more columns) so one axis stays readable.
• On the web, a Dune widget that arrives with a shared or imported board shows Dune works in Cashboard Desktop with Get Cashboard Desktop and Open <title> on dune.com. See Cashboard Desktop and lifetime access.

Pairs well with Chain pulse, Market flows, Stablecoin risk. See the Dune query widget page for a ready-made board.

Shows what one tool of an MCP server you connected returns, as plain text, a table, a list of fields or a number. It calls only the tool and arguments you saved, on a timer, and never acts on the answer.

What it shows

• A new widget shows Choose a server and the setup form: Server, Tool, the arguments the tool asks for, Refresh every (seconds) and Show as (Auto, Table, Key and value, One number, Plain text).
• The result, with the server name as the source line and Updated <age> in the header pill. Images and audio are not shown.
• When a refresh fails after a success, the last result stays, dimmed, under an amber bar that gives its age and the reason.

How to use it

• Add a server under Connections, then MCP servers, and press Test to see its tool count.
• Pick the server and the tool. Only tools the server marks as read-only are listed. Show tools that may change things lists the others, and choosing one needs Allow this tool in this widget.
• Fill the arguments. Strings, numbers, true or false and fixed choices have their own fields; anything else goes in Other arguments (JSON object).
• The gear icon (Change tool or arguments) reopens the setup, and the refresh icon calls the tool now.

Settings

Data and refresh

• The call runs in the app's main process, which holds the server address and token. The widget receives only the result. A call waits at most 20 seconds, and a result over 256 KB is cut with a notice.
• The result is displayed as text. It is never read as an instruction, never sent to B Cash or any model, and never part of the data an agent can read from your board.

Good to know

• Share links, templates and imported boards keep the widget but remove the server and the arguments, so it opens as an empty Choose a server card and makes no call.
• If the server is removed from Connections, the widget says This server is no longer in your list.
• A local command server runs on your computer with your user rights. Add only programs you trust.

Pairs well with Dune query.