Holdings
Back to OverviewAtrium XBT
–Visible to anyone with dashboard access · a new wallet appears within a few seconds
Holdings by collection
Valued from recent sales: the median of at least 3 sales our node saw in 90 daysCollections
Source: our node's sales: sale value is the median of at least 3 clean sales in 90 days · 7-day change, volume, sales and buyers from the same sales
Market pulse
Sales activity
Last 30 daysValue change over 7 days, top collections
What you paid for each inscription (from a sale our node saw, or traced back through our ord index to the purchase, mint or transfer that brought it in), set against what it's worth now at the valuation above. Network fees you paid count as cost. Runes use the average price of the buys our node saw in the last 30 days.
Bitmap districts
Value from recent sales · our nodeNo Bitmap districts in your tracked wallets.
Valued at one figure for every district: the median of at least 3 sales of valid district claims our node saw in 90 days. A district's own number (round, historic, or low) can carry a real premium over that, which this doesn't capture.
Rare sats
Ordinal Theory rarity · sourced from our own nodeNo rare sats found yet. They show up here once our ord index tracks individual sats.
Individually notable satoshis (by mining order and block-boundary position), not a market valuation. A rarity tier isn't a price, so none is shown. Pizza sats are the sats Laszlo Hanyecz paid for two pizzas on 22 May 2010 (10,000 BTC, block 57,043), counted by the sat and traced from that payment by our own node. Requires a fully-synced ord index built with --index-sats; empty until that cutover is done.
Wallet activity
– CSVBalance check: our node vs our own ord index
Our node's count of confirmed coins at each tracked address, next to our own ord index's total (spendable + inscription-held). A difference usually means one side hasn't caught up with the latest block yet; a lasting one is worth a look.
Asset mix
what you hold, by valueRunes & tokens
Priced at current market rateNo runes or tokens in your tracked wallets.
Signals
Chain calendar
Watchlist movers
since you last lookedLeading markets
Value and sales from our nodeNone of the collections you hold has a sale our node saw in 90 days.
Price cross-checks
–Nothing to cross-check yet: a check needs 3 sales of a collection in the last 7 days.
Bitcoin in the news
–No news to show right now.
Block view
–Every square is one transaction, sized by how much block space it takes. Left of the divider are the blocks waiting in our node's mempool (next block closest to the divider); right of it are the blocks just mined. Hover a square for details; click it to open the transaction. Click a protocol below to filter it out of the grid.
Protocol mix
–Every pending transaction in our own node's mempool, checked for a Runestone output or an inscription envelope. Only brand-new inscriptions and rune actions are visible this way. Moving an already-inscribed sat looks like a plain transfer until the ord index can tell them apart.
What's in "Other OP_RETURN"
Read from the data each transaction carries after OP_RETURN, by its first bytes. A prefix gets its own line once three or more pending transactions share it; one-off hashes and messages are pooled. Names marked "likely" come from public docs, not the protocols' own code.
Protocol share by block
–Show as table
Mempool over time
– CSVShow as table
Mempool Pulse
–Stuck transaction?
check a pending transactionBeing bought right now
–Marketplace purchases of inscriptions waiting in our node's mempool: signed listings that someone has filled but that aren't in a block yet. Which item each one moves comes from our own ord index (once it has caught up), from an earlier sale of the same item, or from the transaction that minted it. They're ringed in the block view at the top of this tab.
No inscription purchases waiting in the mempool right now.
Mempool mix
by protocol, nowWhat it costs to get in
fee rates in the upcoming blocks–
Cheapest times to send
––
How this is worked out
For every block our node has seen in the last four weeks, the fee rate at its 10th percentile: the rate that reliably got in (the very bottom of a block is often odd cases, like a pool's own payouts). Grouped by day and hour in your time zone, the middle value of each. Four weeks holds only four Monday 9ams (about two dozen blocks), so a single spike can move one square. "Right now" is the same 10th percentile, for the next projected block. It's the market's habit, not a promise.
The gallery
Every inscription this wallet holdsWallets of interest
–Other people's wallets you want to keep an eye on: whales, collection deployers, market makers. Kept separate from your own wallets: they don't count toward your portfolio. Balances and activity come from our node; this tab doesn't show which NFTs or runes they hold.
Add a wallet
Activity CSV
Runes & BRC-20
–Watch a rune or BRC-20 ticker
Mint radar
–What people are minting, etching and inscribing, read straight from our node. "Pending now" is everything waiting in our node's mempool; the other two add up the blocks mined in that window. These are attempts announced on-chain. A mint past a rune's cap, or a BRC-20 mint over supply, still counts here, because only a full ord index can say whether it took.
Heatmap
–Show as table
Most-minted runes
share of rune mints · avg feeNew rune etchings
newest firstBRC-20 activity
operations by tickerOther token protocols
Inscriptions
by contentBusiest parent collections
Names & districts
Open rune mints
–How mints and ETAs are counted
Terms (amount per mint, cap, and the blocks when minting is allowed) are read from each rune's etching transaction on our node. Mints so far come from our ord index when its rune index is ready; until then, from every block this dashboard has processed: exact for a rune etched since then, "at least" for an older one. The ETA is the blocks left at the pace of the last six blocks, or until the minting window closes, whichever is sooner. Mints come in bursts, so it's a pace, not a promise.
Which pools mine inscriptions
–How filtering is detected
Two measures, over the last 30 days. Share: how much of each pool's blocks (by size) were inscriptions, BRC-20 and runes, against the network's average. Left out: when a block arrives, our node compares its own mempool with what the pool mined. It counts the transactions that had been waiting at least 2 minutes and paid (with their ancestors) at least 1.1× the block's 25th-percentile rate, meaning the pool could clearly have included them, and how many of those it left out, for inscriptions/runes and for ordinary transactions. Every pool leaves some out (propagation, timing), so ordinary transactions are the baseline. A pool leaving out most well-paying inscriptions, while including ordinary ones at the same rates, is filtering. Pools are named from the tag in their coinbase, which a pool can set to anything. Left-out figures only come from blocks processed live.
New collection radar
–No new collection is minting fast right now.
What counts as new
A parent inscription whose children our node first saw being minted in the last 7 days (and at least a day after its block history begins, so an old collection isn't new just because the history is short), minting at least 5 children in the last 24 hours or with 5 waiting in the mempool. Ones the Wizards of Ord registry already lists are marked. Nothing here comes from a marketplace; these are often not listed anywhere yet.
Names .sats · .btc · .x …
–Names in your wallets
Busiest namespaces, last 7 days
Latest registrations
How a name is decided
Sats Names are registered by inscribing the name, as plain text (alice.sats) or as {"p":"sns","op":"reg","name":"alice.sats"}. Lower case, everything after the first space ignored, exactly one dot. The first inscription of a name is the real one; later copies are worthless. Our node reads every name inscription from its own blocks: new blocks as they arrive, and older blocks a slice at a time back to the very first inscription. Until that reaches the start, a name can only be called "first since block N": an older copy might still turn up. Cursed inscriptions and chain reorganisations aren't accounted for.
My view
–Pick the cards you want side by side (from the Overview, Gallery, Watchlist, Mempool, Mint radar and Activity) and they'll all be here. Arrange them from the gear menu like any other tab, rename the tab, or add up to five tabs of your own with the + beside it. Saved in this browser, and to your account when you're signed in.
Activity
– All sales, 30 days (CSV)Mostly built from the sales and mints our node sees. The exceptions: RichSwap's pool list (Rune pools) and the BTC price.
Market indexes
100 = Ordinals' first day; Runes' first well-priced day in the last 30What's in them
Ordinals: the ten collections our own node saw sell most by value in 30 days, equal-weighted (geometric average), from each one's daily median sale price; a collection needs 10 clean sales in the 30 days to be in it; wash-flagged and outlier sales are left out. Runes: the ten runes our own node saw trade most by value in 30 days, equal-weighted (geometric average), from each one's daily median price per token; a rune must have traded 30+ times, on most days, to be in it; wash-flagged trades are left out, and a day's price more than 5× away from a rune's own typical price is treated as bad data and skipped. Both are today's top ten tracked back, which flatters the past a little. Equal weight measures the market's breadth rather than one giant.
Hot runes
last 24 hours against the days before CSVHow runes are picked
A rune needs at least 3 sales and 0.01 BTC traded in the last 24 hours, with at least one buyer and two wallets in all that aren't pools or market makers. It is then scored on three things, each against its own recent days:
- Volume: how many times its usual daily volume traded today.
- Buyers: how many different wallets bought today, against its usual day. “New” counts wallets that hadn't bought or sold it earlier in the week.
- Price: today's volume-weighted median price against the days before (only when both sides have 3+ priced sales).
A rune with no sales in the days before is marked New market. Looks like warns when the name is a letter or two away from a much bigger rune, a common copycat trick. Needs at least a day of stored history to compare with.
Hot BRC-20 tickers
last 24 hours against the days beforeHow tickers are picked
A ticker needs at least 3 sales and 0.01 BTC traded in the last 24 hours, with at least one buyer and two wallets in all that aren't pools or market makers. It is then scored on volume, buyers and price against its own recent days, using the same scoring function Hot runes uses, so a 3.2 here and a 3.2 there mean the same thing.
Every number comes from sales this node found in blocks: the ticker is written in the transfer inscription's own content, the price is what the buyer paid, and the buyers are the addresses that paid. No outside data is involved, which is what separates this list from Hot collections above it.
Hot collections
last 24 hours against the days beforeHow collections are picked
A collection needs at least 3 sales and 0.01 BTC traded in the last 24 hours. It is then scored on three things, each against its own recent days, with the same scoring as Hot runes, so a 3.2 here means what a 3.2 there does:
- Volume: how much traded today against its usual day.
- Sales: how many sales today against its usual day.
- Value: the 7-day move in its value from recent sales.
Read from our node, like the rest of this tab: every collection sale our node saw in the last 90 days, wash-flagged and outlier sales left out, with membership from the collection registry.
Hot runes counts distinct buyers per day, which is what separates real interest from one wallet trading with itself. A collection's buyers over a week can't be split into days the same way, so this uses sales instead. That's a weaker signal, and worth knowing when reading the two lists side by side.
Sales in the mempool
–Underpriced sales
–How "underpriced" is judged
An item's value is its collection's value from recent sales when it sold (the median of at least 3 sales our node saw in 90 days, recorded hourly; the current value before that history exists, or the collection's median sale over 30 days when it has none), times its measured trait premium when one of its traits has enough sales behind it. A sale at least 30% under that is listed. Pending purchases in the mempool are included and marked. Nothing is listed for a collection we can't place or price.
Measurement, not advice. Every number here is a measurement of what already happened (or is already sitting in the mempool) on the public chain -- nothing on this card recommends buying, selling or holding anything. How every figure on this dashboard is sourced · Full track record
Top inscription flippers
–How flips are counted
A flip is a wallet buying an inscription and later selling that same inscription, both sales seen by our node (it keeps the last 30 days). Profit is the sale price minus the purchase price, before network fees. Wallets need at least 3 flips to be ranked; marketplaces, pools and self-trades are left out.
Measurement, not advice. Every number here is a measurement of what already happened (or is already sitting in the mempool) on the public chain -- nothing on this card recommends buying, selling or holding anything. How every figure on this dashboard is sourced · Full track record
Rune pools
–What these numbers are
RichSwap runs on-chain rune pools (Omnity's Runes Exchange Environment): each pool is one Bitcoin address holding BTC and one rune, and a trade swaps against it. Pool price, spread, 24h volume and liquidity are RichSwap's own published figures. BTC in pool is what our node saw at the pool's address at its last reading (every 6 hours), and its 7-day change shows liquidity arriving or leaving. Market is the median price the same rune traded at elsewhere, from trades our node classified (last 24 hours, or 7 days when there are fewer than 3), and vs market is how much dearer (+) or cheaper (−) the pool is. The rune side of each pool needs our ord index and isn't shown yet.
Wash trading
–What gets flagged, and what happens
A sale is flagged when buyer and seller are the same address; when the same item goes A→B and back B→A (runes: within 7 days); when the same two wallets trade with each other 3 or more times in 30 days, in both directions (one direction is just a collector sweeping a seller's listings); or when the buyer's payment includes coins from the seller's own address. Known marketplaces, pools and desks are exempt from the pair rules. Flagged sales stay visible, marked possible wash, but are left out of hot lists, flipper rankings, trait premiums, underpriced sales, collection medians, rune Greeks, pool comparisons and the Runes index. A flag describes a pattern, not intent.
Activity feed
last 7 days CSVWhat makes a signal
A buy or sell appears when the wallet on that side is one of yours, on your watchlist, a Whale or Smart wallet, or when the trade is Big (at least 0.02 BTC and among the week's biggest 10%).
- Whale: top 3% of wallets by traded volume this week (at least 0.25 BTC), or a single trade of 1 BTC or more.
- Smart: made at least 25,000 sats on runes it bought and sold this week, winning on 60%+ of 2 or more sales.
- Venue: liquidity pools and market makers. They trade with everyone, so their side of a trade is never a signal.
Watched lists every sale and minting surge of the runes and BRC-20 tickers on your watchlist; in the other views they carry a binoculars mark.
Mint signals: a rune or BRC-20 ticker minted at least 3× faster in the last hour than in the six before, a rune etched in the last day with an open mint that already has 25+ mints, and anything your own or watched wallets mint.
Measurement, not advice. Every number here is a measurement of what already happened (or is already sitting in the mempool) on the public chain -- nothing on this card recommends buying, selling or holding anything, including the Whale and Smart badges. How every figure on this dashboard is sourced · Full track record
Rune market Greeks
– CSVColumns
What the letters mean
Real Greeks describe option prices. Runes have no options market, so the letters are borrowed for their plain meaning. Prices are sats per whole token, worked out from what each buyer paid and received.
- Δ delta: price change: the last 24 hours against the 24 hours before, and against the start of the week.
- Γ gamma: the change in that change. Positive means the move is speeding up (or a fall is slowing).
- Θ theta: steady drift per day across the week, ignoring the day-to-day noise.
- ν vega: volatility: the typical size of a day's price move.
- β beta: how much the rune moves with the rest of the rune market (1 = in step, 0 = unrelated, negative = the opposite way). β BTC is the same against bitcoin in dollar terms; it needs 14 days of daily prices.
- α alpha: return per day beyond what β explains: doing better (or worse) than the market.
Confidence reflects how many sales and price steps there are. With thin trading these numbers swing a lot, so treat “low” as a hint, not a measurement.
Inscription sales
last 7 days CSVHow sales are found
Every block our node receives is checked for marketplace listings: an input signed the way listings are (SIGHASH_SINGLE|ANYONECANPAY) with no rune data. The output paired with that input is the seller's payment, so the price, seller and buyer come straight from the transaction.
Which inscription changed hands is worked out three ways: the coin was the one that created the inscription (sold right after minting), the same item went through an earlier or later sale here (a flip), or (once our ord index is ready) ord says what arrived in the buyer's output. ord can only tell while the buyer still holds the item, so older sales of items that moved on stay not identified; their price still counts.
Collection is the parent inscription. It gets a name when one of your holdings with the same parent has one. BRC-20 transfer inscriptions are grouped by ticker, with the price per token.