Table · StrataPlanned

Bitcoin Runes List: Top Runes by Holders and Mints

Which Bitcoin runes have the most holders and mints, and which can still be minted?

Every rune etched on Bitcoin with its holders, supply, mints, premine and whether it can still be minted, read under the Runes rules.

ShareEmail itvoltfincrypto.com/apps/bitcoin-runes-list
Blueprint

What the table will hold.

The table as it will open in Strata. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.

One row One row per rune, on the latest complete daySorted by Holders, highest first

RuneRune IDEtchedHoldersSupplyPremineMintsMint statusBurnedTransfers, 30 daysReceipt
Rune rune Text
The rune's name with its spacers and symbol, as set in the etching.
Rune ID rune_id Text
The block and transaction index of the etching, which identify the rune exactly.
Etched etched Date
Date of the block that confirmed the etching.
Holders holders Number
Addresses whose unspent outputs carry a non-zero balance of the rune.
Supply supply Exact amount
Premine plus completed mints minus burned runes, scaled by the rune's divisibility.
Premine premine_share Percent
The etcher's premine as a share of supply.
Mints mints Number
Mint instructions that succeeded, shown against the cap where one is set.
Mint status mint_status Text
Open, not yet open, closed or minted out, from the terms and the latest block.
Burned burned Exact amount
Runes destroyed by cenotaphs and by edicts to OP_RETURN outputs.
Transfers, 30 days transfers_30d Number
Transactions that moved the rune in the last 30 days.
Receipt receipt Link
The etching transaction and the block the row was read at.

Filter by Mint status.

About

What it answers, and for whom.

Runes are fungible tokens on Bitcoin, launched with the 2024 halving. A rune is created by an etching, issued by mints and moved by edicts, all written in a runestone: an OP_RETURN output in an ordinary Bitcoin transaction. Balances live on unspent outputs rather than in accounts, so this table decodes every runestone, applies the protocol's rules and adds up which outputs hold which runes.

Sort it by holders to see which runes are widely held and by mints to see which drew the most demand at launch, then filter it to runes whose mint terms are still open. Each row also shows how much was premined to the etcher and how much was burned, because a rune's supply is only as clear as those two numbers.

Method

How it will be measured.

Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.

How receipts work →
  1. Runestones are decoded from outputs whose script starts with OP_RETURN followed by OP_13, following the Runes specification for etchings, mints, edicts and cenotaphs.
  2. Balances are tracked per unspent output; holders are distinct addresses whose unspent outputs carry a non-zero balance of the rune at the latest day's last block.
  3. Supply is premine plus completed mints minus burned runes, where burns include cenotaphs and edicts that send runes to an OP_RETURN output.
  4. Mint status reads the rune's terms (amount per mint, cap and height or offset window) against the latest block: open, not yet open, closed or minted out.

The data it needs

Read from chain state and history

  • bitcoin_inscriptions_dailyTo buildOrdinals, runes and BRC-20Inscriptions, rune etchings and mints, BRC-20 transfers, and the fees they paid per day.
  • address_labelsTo buildAddress labelsLabels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
  • Runestones in OP_RETURN outputs of every Bitcoin block since the 2024 halving
  • Rune balances per unspent output, computed under the Runes protocol rules
  • Etching fields: name, spacers, divisibility, symbol, premine, terms and turbo flag
  • Spends of rune-bearing outputs, for transfers and burns
Questions

Questions people ask.

What are Bitcoin runes?

A fungible token protocol on Bitcoin, live since the 2024 halving. Runes are etched, minted and transferred through data in OP_RETURN outputs, and balances are attached to unspent outputs, so they move with ordinary Bitcoin transactions.

How do rune mints work?

An etching can set open mint terms: how much each mint creates, how many mints are allowed and when they may happen. Anyone can then mint by writing a mint instruction in a runestone, until the cap is reached or the window ends.

What is a rune premine?

The amount the etcher allocates to themselves at creation, before anyone mints. Some runes are fully premined and have no open mint, so the table shows the premine as a share of supply.

Can runes be lost or burned?

Yes. A malformed runestone, called a cenotaph, burns the runes in its inputs, and an edict can send runes to an OP_RETURN output on purpose. A wallet that does not understand runes can also move them by mistake: with no runestone, they go to the first output that is not OP_RETURN.

What is a rune ID?

The block height and transaction index of the etching, written as two numbers joined by a colon. It identifies a rune exactly, while its name, made of letters with optional spacers, is for people.

Runestone
An OP_RETURN output carrying a Runes protocol message: an etching, a mint, edicts or a pointer.
Etching
The transaction that creates a rune and sets its name, divisibility, symbol, premine and mint terms.
Cenotaph
A malformed runestone. Its input runes are burned, a rune it etches can never be minted and a mint it carries is burned.
Edict
An instruction in a runestone that moves an amount of a rune to one of the transaction's outputs.

Build Bitcoin Runes List: Top Runes by Holders and Mints on verified data.

Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.