{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "anatomy-of-a-bitcoin-block",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/anatomy-of-a-bitcoin-block/",
  "collection": "bitcoin",
  "title": "Anatomy of a Bitcoin block: the header, the coinbase and the weight limit, using block 0",
  "description": "Inside a Bitcoin block: the six header fields, the coinbase transaction that mints new coins, and how size and weight are counted, with block 0 as the example.",
  "aliases": [
    "bitcoin block",
    "block header",
    "coinbase transaction",
    "merkle root",
    "nonce",
    "block weight",
    "what is in a bitcoin block"
  ],
  "dates": {
    "published": "2026-09-23",
    "modified": "2026-10-02",
    "verified": "2026-10-02T16:01:48.343Z",
    "dataAsOf": null
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "A Bitcoin block is an 80-byte header followed by a list of transactions. The header holds six fields: a version number, the hash of the previous block, a Merkle root that summarizes every transaction, a timestamp, an encoded difficulty target, and a nonce that miners change while searching for a valid hash. The first transaction, the coinbase, creates the block reward. Block 0, mined on 3 January 2009, is 285 bytes and holds a single transaction.",
    "claimId": "anatomy-of-a-bitcoin-block-quick-answer",
    "sourceIds": [
      "devref-block-chain",
      "devref-transactions",
      "bip141"
    ]
  },
  "keyFacts": [
    {
      "label": "Header size",
      "value": "80 bytes, in six fields",
      "sourceIds": [
        "devref-block-chain",
        "whitepaper"
      ],
      "id": "header-size",
      "claimId": "anatomy-of-a-bitcoin-block-fact-header-size"
    },
    {
      "label": "Header fields",
      "value": "Version (4 bytes), previous block hash (32), Merkle root (32), time (4), nBits (4), nonce (4)",
      "sourceIds": [
        "devref-block-chain"
      ],
      "id": "header-fields",
      "claimId": "anatomy-of-a-bitcoin-block-fact-header-fields"
    },
    {
      "label": "Block 0 mined",
      "value": "3 January 2009, 18:15:05 UTC (Unix time 1231006505)",
      "sourceIds": [
        "wiki-genesis-block",
        "blockstream-block-0"
      ],
      "id": "block-0-mined",
      "claimId": "anatomy-of-a-bitcoin-block-fact-block-0-mined"
    },
    {
      "label": "Block 0 size",
      "value": "285 bytes, 1,140 weight units, one transaction",
      "sourceIds": [
        "blockstream-block-0"
      ],
      "id": "block-0-size",
      "claimId": "anatomy-of-a-bitcoin-block-fact-block-0-size"
    },
    {
      "label": "Block 0 nonce and bits",
      "value": "Nonce 2083236893; bits 0x1d00ffff, which is difficulty 1",
      "sourceIds": [
        "blockstream-block-0",
        "wiki-genesis-block",
        "devref-block-chain"
      ],
      "id": "block-0-nonce-and-bits",
      "claimId": "anatomy-of-a-bitcoin-block-fact-block-0-nonce-and-bits"
    },
    {
      "label": "Weight limit",
      "value": "4,000,000 weight units per block; before SegWit the limit was 1,000,000 bytes",
      "sourceIds": [
        "bip141"
      ],
      "id": "weight-limit",
      "claimId": "anatomy-of-a-bitcoin-block-fact-weight-limit"
    },
    {
      "label": "Coinbase maturity",
      "value": "A coinbase output cannot be spent for at least 100 blocks",
      "sourceIds": [
        "devguide-block-chain"
      ],
      "id": "coinbase-maturity",
      "claimId": "anatomy-of-a-bitcoin-block-fact-coinbase-maturity"
    },
    {
      "label": "Height in coinbase",
      "value": "Required since block 227,836 under BIP34",
      "sourceIds": [
        "bip34",
        "devref-transactions"
      ],
      "id": "height-in-coinbase",
      "claimId": "anatomy-of-a-bitcoin-block-fact-height-in-coinbase"
    }
  ],
  "prerequisites": [],
  "sections": [
    {
      "id": "header-plus-transactions",
      "heading": "A block is a short header and a long list of transactions",
      "sourceIds": [
        "whitepaper",
        "devref-block-chain",
        "devguide-block-chain"
      ],
      "paragraphs": [
        "Strip away the mystique and a block is a small, fixed-size header followed by however many transactions the miner chose to include. The header is 80 bytes, a size the white paper gives in passing when it estimates that headers alone would add up to 4.2 megabytes a year at one block every ten minutes. Everything that makes a block a block, the proof-of-work, the link to the previous block, the fingerprint of its contents, lives in those 80 bytes. The transactions are the cargo.",
        "When people talk about a block’s hash, they mean the hash of the header only. Miners hash the header repeatedly, and the developer guide notes that each block header must hash to a value below the target threshold. The transactions are not hashed directly during mining; they are represented in the header by a single 32-byte summary, which is what lets a miner try enormous numbers of header variations without touching the transaction list. Our [what is a blockchain](/encyclopedia/what-is-a-blockchain/) article explains how those headers chain together."
      ]
    },
    {
      "id": "six-fields-block-0",
      "heading": "The six header fields, read off block 0",
      "sourceIds": [
        "devref-block-chain",
        "blockstream-block-0",
        "wiki-genesis-block"
      ],
      "paragraphs": [
        "The developer reference lists the header fields in order. Version, four bytes, says which validation rules the block follows. Previous block header hash, 32 bytes, is the hash of the block before, which the reference says ensures no previous block can be changed without also changing this block’s header. Merkle root, 32 bytes, is derived from the hashes of all the transactions in the block. Time, four bytes, is the Unix time when the miner started hashing, and it must be greater than the median time of the previous eleven blocks. nBits, four bytes, is the encoded target the header hash must fall below. Nonce, four bytes, is an arbitrary number miners change to alter the hash.",
        "Block 0, the [genesis block](/encyclopedia/genesis-block-explained/), makes a good worked example because a block explorer shows every field and there is only one transaction to think about. Its version is 1. It has no previous block to point to; the Bitcoin Wiki notes that it does not reference a previous block. Its Merkle root is simply the identifier of its one transaction, which begins 4a5e1e. Its time is 1231006505, which is 3 January 2009 at 18:15:05 UTC. Its nBits value is 0x1d00ffff, the easiest target the main network allows, which the developer reference identifies as difficulty 1, and the explorer reports its difficulty as exactly 1. Its nonce is 2083236893.",
        "One oddity: the wiki points out that the genesis block’s hash has two more leading zeros than an early block needed, meaning Satoshi found a hash far below the target, and that the next block’s timestamp is a full six days later. Nobody knows why. The header records what happened, not what was intended."
      ]
    },
    {
      "id": "coinbase-transaction",
      "heading": "The coinbase transaction is where new bitcoin comes from",
      "sourceIds": [
        "whitepaper",
        "devref-transactions",
        "bip34",
        "wiki-genesis-block",
        "devguide-block-chain",
        "devref-block-chain"
      ],
      "paragraphs": [
        "The white paper says that by convention the first transaction in a block is a special one that starts a new coin owned by the block’s creator. That is the coinbase transaction. Unlike every other transaction, it spends nothing. The developer reference describes its single input as pointing at a 32-byte null with an index of 0xffffffff, a placeholder meaning no previous output, followed by a script of between 2 and 100 bytes that the miner fills in more or less as it likes.",
        "Since BIP34, proposed by Gavin Andresen on 6 July 2012, that script must begin with the block’s height, so that no two coinbase transactions can be identical. The developer reference notes that blocks before height 227,836 did not require it, and BIP34 records that block 227,835, on 24 March 2013, was the last version 1 block. The rest of the space is arbitrary data. Miners commonly put an extra nonce there, which changes the Merkle root and gives them a fresh header to search when the four-byte nonce runs out. Some also leave messages. Satoshi did: block 0’s coinbase carries the text “The Times 03/Jan/2009 Chancellor on brink of second bailout for banks.”",
        "The coinbase output collects the block reward and every fee in the block, and it comes with a waiting period: the developer guide states that a coinbase output cannot be spent for at least 100 blocks. Block 0’s single output was 50 bitcoin, and it has never moved, because, as the wiki explains, a quirk in how the genesis block is expressed in the code means it cannot be spent. Whether that was deliberate is unknown. The coins sit at the address recorded in our [genesis block coinbase](/wallet/genesis-block-coinbase-block-0/) dossier."
      ]
    },
    {
      "id": "merkle-root",
      "heading": "The Merkle root ties every transaction to the header",
      "sourceIds": [
        "devguide-block-chain",
        "devref-block-chain",
        "whitepaper"
      ],
      "paragraphs": [
        "The developer guide describes how the root is built. Each transaction identifier is paired with another and the pair is hashed together; if there is an odd number, the one without a partner is hashed with a copy of itself. The resulting hashes are paired and hashed again, and so on, until one hash remains: the Merkle root. The coinbase transaction’s identifier always goes first. Change one byte of one transaction and the root changes, which changes the header, which changes the block hash, which would no longer satisfy the proof-of-work.",
        "The white paper introduced the structure for a practical reason: disk space. Old transactions could be pruned away while the root in the header stayed valid, and a light client could check that a transaction was in a block by asking for the short branch of hashes linking it to the root, without downloading the block. That is the Merkle branch in the paper’s payment-verification section, and it is why a phone wallet can confirm a payment while holding only headers. The [nodes](/encyclopedia/bitcoin-nodes-explained/) article covers what a light client gives up by doing so."
      ]
    },
    {
      "id": "size-and-weight",
      "heading": "Size versus weight: how big a block can be",
      "sourceIds": [
        "bip141",
        "blockstream-block-0"
      ],
      "paragraphs": [
        "Originally Bitcoin had one limit: BIP141 records that blocks were limited to 1,000,000 bytes. The Segregated Witness upgrade, specified in that BIP by Eric Lombrozo, Johnson Lau and Pieter Wuille, replaced the byte count with a new measure. Block weight is the base size, meaning the block serialized the old way without signature data, times three, plus the total size including that data. A block’s weight must be no more than 4,000,000 units.",
        "The effect is that signature data counts a quarter as much as everything else, which is why a block can be larger than a megabyte on disk while its weight stays under the cap. Block 0 makes the arithmetic visible. It is 285 bytes and has no witness data, so its base size and total size are the same, and its weight is 285 times three plus 285, which is 1,140, exactly what the explorer reports. A transaction’s virtual size, the number wallets use when they quote fees in satoshis per virtual byte, is its weight divided by four, rounded up to a whole virtual byte.",
        "That limit was the subject of a years-long argument covered in the [block size war](/history/bitcoin-block-size-war/) dossier, and it is the reason [fees](/encyclopedia/bitcoin-transaction-fees-and-mempool/) rise when demand does. The [SegWit](/encyclopedia/segwit-explained/) article explains where witness data went and why. If you want to inspect any of these fields yourself, our guide to [reading a block explorer](/encyclopedia/how-to-read-a-block-explorer/) shows where each one appears."
      ]
    }
  ],
  "faq": [
    {
      "question": "How big is a Bitcoin block?",
      "answer": "The limit is 4,000,000 weight units, where weight is the block’s base size times three plus its total size including signature data. Before Segregated Witness the limit was 1,000,000 bytes. A block full of ordinary transactions comes in well under four megabytes on disk because most of its bytes are counted at full weight.",
      "sourceIds": [
        "bip141"
      ]
    },
    {
      "question": "What is the nonce in a Bitcoin block?",
      "answer": "A four-byte number in the header that miners change to produce a different hash on each attempt. When all four billion or so values are used up, miners change an extra nonce in the coinbase transaction instead, which alters the Merkle root and gives them a fresh header to search.",
      "sourceIds": [
        "devref-block-chain",
        "devref-transactions"
      ]
    },
    {
      "question": "What is the coinbase transaction?",
      "answer": "The first transaction in every block. It has no real input, creates the block reward plus the block’s fees as new outputs for the miner, must include the block height since BIP34, and its output cannot be spent for at least 100 blocks.",
      "sourceIds": [
        "whitepaper",
        "devref-transactions",
        "devguide-block-chain",
        "bip34"
      ]
    },
    {
      "question": "When was block 0 mined?",
      "answer": "Its header timestamp is 1231006505, which is 3 January 2009 at 18:15:05 UTC. It is 285 bytes, contains one transaction, was mined at difficulty 1 with nonce 2083236893, and the next block did not appear until six days later.",
      "sourceIds": [
        "wiki-genesis-block",
        "blockstream-block-0"
      ]
    },
    {
      "question": "What is the Merkle root?",
      "answer": "A single 32-byte hash in the header that summarizes every transaction in the block. Transaction identifiers are hashed together in pairs, then the results are paired and hashed again, until one hash is left. Changing any transaction changes the root and therefore the block’s hash.",
      "sourceIds": [
        "devguide-block-chain",
        "devref-block-chain"
      ]
    }
  ],
  "claims": [
    {
      "id": "anatomy-of-a-bitcoin-block-quick-answer",
      "articleSlug": "anatomy-of-a-bitcoin-block",
      "statement": "A Bitcoin block is an 80-byte header followed by a list of transactions. The header holds six fields: a version number, the hash of the previous block, a Merkle root that summarizes every transaction, a timestamp, an encoded difficulty target, and a nonce that miners change while searching for a valid hash. The first transaction, the coinbase, creates the block reward. Block 0, mined on 3 January 2009, is 285 bytes and holds a single transaction.",
      "sourceIds": [
        "source-1f428f4e78a3eded",
        "source-26fc928b4956daf4",
        "source-896e868816ad19d1"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-1f428f4e78a3eded",
          "locator": "Lists the six 80-byte header fields with sizes and meanings, the median-time rule for timestamps, the nBits encoding with 0x1d00ffff as difficulty 1 on mainnet, and states that the coinbase txid is placed first and collects rewards and fees."
        },
        {
          "sourceId": "source-26fc928b4956daf4",
          "locator": "Describes the coinbase input as a null outpoint with index 0xffffffff, a script of 2 to 100 bytes beginning with the block height under BIP34 since height 227,836, and the extra nonce miners put in the remaining space."
        },
        {
          "sourceId": "source-896e868816ad19d1",
          "locator": "Records the earlier 1,000,000-byte limit and defines base size, total size, block weight as base size times three plus total size with a 4,000,000 limit, and virtual size as weight divided by four, rounded up to a whole virtual byte rounded up."
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T16:01:48.343Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Checked block-header and raw-transaction references, actual genesis/Finney block data, and BIP141 block-weight accounting."
        ]
      }
    },
    {
      "id": "anatomy-of-a-bitcoin-block-fact-header-size",
      "articleSlug": "anatomy-of-a-bitcoin-block",
      "statement": "Header size: 80 bytes, in six fields",
      "sourceIds": [
        "source-1f428f4e78a3eded",
        "source-0e46aca4dbc5a030"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-1f428f4e78a3eded",
          "locator": "Lists the six 80-byte header fields with sizes and meanings, the median-time rule for timestamps, the nBits encoding with 0x1d00ffff as difficulty 1 on mainnet, and states that the coinbase txid is placed first and collects rewards and fees."
        },
        {
          "sourceId": "source-0e46aca4dbc5a030",
          "locator": "Section 6 describes the first transaction in a block creating a new coin for its creator; section 7 gives the 80-byte header, the 4.2 MB per year estimate and the Merkle tree; section 8 describes verifying a payment from a Merkle branch."
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T16:01:48.343Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Checked block-header and raw-transaction references, actual genesis/Finney block data, and BIP141 block-weight accounting."
        ]
      }
    },
    {
      "id": "anatomy-of-a-bitcoin-block-fact-header-fields",
      "articleSlug": "anatomy-of-a-bitcoin-block",
      "statement": "Header fields: Version (4 bytes), previous block hash (32), Merkle root (32), time (4), nBits (4), nonce (4)",
      "sourceIds": [
        "source-1f428f4e78a3eded"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-1f428f4e78a3eded",
          "locator": "Lists the six 80-byte header fields with sizes and meanings, the median-time rule for timestamps, the nBits encoding with 0x1d00ffff as difficulty 1 on mainnet, and states that the coinbase txid is placed first and collects rewards and fees."
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T16:01:48.343Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Checked block-header and raw-transaction references, actual genesis/Finney block data, and BIP141 block-weight accounting."
        ]
      }
    },
    {
      "id": "anatomy-of-a-bitcoin-block-fact-block-0-mined",
      "articleSlug": "anatomy-of-a-bitcoin-block",
      "statement": "Block 0 mined: 3 January 2009, 18:15:05 UTC (Unix time 1231006505)",
      "sourceIds": [
        "source-d2c36e64f08016f8",
        "source-691e2f1a1d0a41de"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-d2c36e64f08016f8",
          "locator": "Community reference giving the timestamp of 1231006505, the coinbase headline text, the unspendable 50 bitcoin reward and its cause, the extra leading zeros in the hash, the six-day gap to block 1, and that block 0 references no previous block."
        },
        {
          "sourceId": "source-691e2f1a1d0a41de",
          "locator": "Reports block 0 as height 0, version 1, timestamp 1231006505, one transaction, size 285 bytes, weight 1140, bits 486604799, nonce 2083236893, difficulty 1.0, with a Merkle root beginning 4a5e1e."
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T16:01:48.343Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Checked block-header and raw-transaction references, actual genesis/Finney block data, and BIP141 block-weight accounting."
        ]
      }
    },
    {
      "id": "anatomy-of-a-bitcoin-block-fact-block-0-size",
      "articleSlug": "anatomy-of-a-bitcoin-block",
      "statement": "Block 0 size: 285 bytes, 1,140 weight units, one transaction",
      "sourceIds": [
        "source-691e2f1a1d0a41de"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-691e2f1a1d0a41de",
          "locator": "Reports block 0 as height 0, version 1, timestamp 1231006505, one transaction, size 285 bytes, weight 1140, bits 486604799, nonce 2083236893, difficulty 1.0, with a Merkle root beginning 4a5e1e."
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T16:01:48.343Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Checked block-header and raw-transaction references, actual genesis/Finney block data, and BIP141 block-weight accounting."
        ]
      }
    },
    {
      "id": "anatomy-of-a-bitcoin-block-fact-block-0-nonce-and-bits",
      "articleSlug": "anatomy-of-a-bitcoin-block",
      "statement": "Block 0 nonce and bits: Nonce 2083236893; bits 0x1d00ffff, which is difficulty 1",
      "sourceIds": [
        "source-691e2f1a1d0a41de",
        "source-d2c36e64f08016f8",
        "source-1f428f4e78a3eded"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-691e2f1a1d0a41de",
          "locator": "Reports block 0 as height 0, version 1, timestamp 1231006505, one transaction, size 285 bytes, weight 1140, bits 486604799, nonce 2083236893, difficulty 1.0, with a Merkle root beginning 4a5e1e."
        },
        {
          "sourceId": "source-d2c36e64f08016f8",
          "locator": "Community reference giving the timestamp of 1231006505, the coinbase headline text, the unspendable 50 bitcoin reward and its cause, the extra leading zeros in the hash, the six-day gap to block 1, and that block 0 references no previous block."
        },
        {
          "sourceId": "source-1f428f4e78a3eded",
          "locator": "Lists the six 80-byte header fields with sizes and meanings, the median-time rule for timestamps, the nBits encoding with 0x1d00ffff as difficulty 1 on mainnet, and states that the coinbase txid is placed first and collects rewards and fees."
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T16:01:48.343Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Checked block-header and raw-transaction references, actual genesis/Finney block data, and BIP141 block-weight accounting."
        ]
      }
    },
    {
      "id": "anatomy-of-a-bitcoin-block-fact-weight-limit",
      "articleSlug": "anatomy-of-a-bitcoin-block",
      "statement": "Weight limit: 4,000,000 weight units per block; before SegWit the limit was 1,000,000 bytes",
      "sourceIds": [
        "source-896e868816ad19d1"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-896e868816ad19d1",
          "locator": "Records the earlier 1,000,000-byte limit and defines base size, total size, block weight as base size times three plus total size with a 4,000,000 limit, and virtual size as weight divided by four, rounded up to a whole virtual byte rounded up."
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T16:01:48.343Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Checked block-header and raw-transaction references, actual genesis/Finney block data, and BIP141 block-weight accounting."
        ]
      }
    },
    {
      "id": "anatomy-of-a-bitcoin-block-fact-coinbase-maturity",
      "articleSlug": "anatomy-of-a-bitcoin-block",
      "statement": "Coinbase maturity: A coinbase output cannot be spent for at least 100 blocks",
      "sourceIds": [
        "source-190b9fe0eec933dc"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-190b9fe0eec933dc",
          "locator": "States that each header must hash below the target, that a coinbase output cannot be spent for at least 100 blocks, and how the Merkle tree pairs txids, hashing an unpaired txid with a copy of itself."
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T16:01:48.343Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Checked block-header and raw-transaction references, actual genesis/Finney block data, and BIP141 block-weight accounting."
        ]
      }
    },
    {
      "id": "anatomy-of-a-bitcoin-block-fact-height-in-coinbase",
      "articleSlug": "anatomy-of-a-bitcoin-block",
      "statement": "Height in coinbase: Required since block 227,836 under BIP34",
      "sourceIds": [
        "source-138d653a48233984",
        "source-26fc928b4956daf4"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-138d653a48233984",
          "locator": "Requires the block height as the first item in the coinbase script for version 2 blocks, to enforce uniqueness, and records block 227,835 on 24 March 2013 as the last version 1 block."
        },
        {
          "sourceId": "source-26fc928b4956daf4",
          "locator": "Describes the coinbase input as a null outpoint with index 0xffffffff, a script of 2 to 100 bytes beginning with the block height under BIP34 since height 227,836, and the extra nonce miners put in the remaining space."
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T16:01:48.343Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Checked block-header and raw-transaction references, actual genesis/Finney block data, and BIP141 block-weight accounting."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "devref-block-chain",
      "label": "Bitcoin Developer Reference: Block Chain (Block Headers)",
      "publisher": "Bitcoin Project, developer.bitcoin.org",
      "url": "https://developer.bitcoin.org/reference/block_chain.html",
      "note": "Lists the six 80-byte header fields with sizes and meanings, the median-time rule for timestamps, the nBits encoding with 0x1d00ffff as difficulty 1 on mainnet, and states that the coinbase txid is placed first and collects rewards and fees.",
      "checkedAt": "2026-10-02T14:48:37.089132+00:00",
      "contentSha256": "c3f45d19a7af38328bdf5f0691644e5444bf805b6d8f4efa72062b4150db54e3",
      "locator": "Lists the six 80-byte header fields with sizes and meanings, the median-time rule for timestamps, the nBits encoding with 0x1d00ffff as difficulty 1 on mainnet, and states that the coinbase txid is placed first and collects rewards and fees.",
      "recordId": "source-1f428f4e78a3eded",
      "version": null
    },
    {
      "id": "devref-transactions",
      "label": "Bitcoin Developer Reference: Transactions (Coinbase)",
      "publisher": "Bitcoin Project, developer.bitcoin.org",
      "url": "https://developer.bitcoin.org/reference/transactions.html",
      "note": "Describes the coinbase input as a null outpoint with index 0xffffffff, a script of 2 to 100 bytes beginning with the block height under BIP34 since height 227,836, and the extra nonce miners put in the remaining space.",
      "checkedAt": "2026-10-02T14:48:40.879756+00:00",
      "contentSha256": "089c675fe5634001ccae037c578d1e94c7b7b279f57ceb4284a6c07f3315d69d",
      "locator": "Describes the coinbase input as a null outpoint with index 0xffffffff, a script of 2 to 100 bytes beginning with the block height under BIP34 since height 227,836, and the extra nonce miners put in the remaining space.",
      "recordId": "source-26fc928b4956daf4",
      "version": null
    },
    {
      "id": "devguide-block-chain",
      "label": "Bitcoin Developer Guide: Block Chain",
      "publisher": "Bitcoin Project, developer.bitcoin.org",
      "url": "https://developer.bitcoin.org/devguide/block_chain.html",
      "note": "States that each header must hash below the target, that a coinbase output cannot be spent for at least 100 blocks, and how the Merkle tree pairs txids, hashing an unpaired txid with a copy of itself.",
      "checkedAt": "2026-10-02T14:48:36.834850+00:00",
      "contentSha256": "3ddf7f1164ec8d670a5fbbcf7f4aaca7549bbc10c75f0bb3dad930dbfad08a25",
      "locator": "States that each header must hash below the target, that a coinbase output cannot be spent for at least 100 blocks, and how the Merkle tree pairs txids, hashing an unpaired txid with a copy of itself.",
      "recordId": "source-190b9fe0eec933dc",
      "version": null
    },
    {
      "id": "whitepaper",
      "label": "Bitcoin: A Peer-to-Peer Electronic Cash System",
      "publisher": "bitcoin.org",
      "author": "Satoshi Nakamoto",
      "issued": "2008",
      "url": "https://bitcoin.org/bitcoin.pdf",
      "note": "Section 6 describes the first transaction in a block creating a new coin for its creator; section 7 gives the 80-byte header, the 4.2 MB per year estimate and the Merkle tree; section 8 describes verifying a payment from a Merkle branch.",
      "checkedAt": "2026-10-02T15:04:11.761440+00:00",
      "contentSha256": "b1674191a88ec5cdd733e4240a81803105dc412d6c6708d53ab94fc248f4f553",
      "locator": "Section 6 describes the first transaction in a block creating a new coin for its creator; section 7 gives the 80-byte header, the 4.2 MB per year estimate and the Merkle tree; section 8 describes verifying a payment from a Merkle branch.",
      "recordId": "source-0e46aca4dbc5a030",
      "version": null
    },
    {
      "id": "wiki-genesis-block",
      "label": "Genesis block",
      "publisher": "Bitcoin Wiki",
      "url": "https://en.bitcoin.it/wiki/Genesis_block",
      "note": "Community reference giving the timestamp of 1231006505, the coinbase headline text, the unspendable 50 bitcoin reward and its cause, the extra leading zeros in the hash, the six-day gap to block 1, and that block 0 references no previous block.",
      "checkedAt": "2026-10-02T14:48:36.889384+00:00",
      "contentSha256": "ba659aae4b756e045488615fe0d59da67e2a91aec1431bf84786d14237266a6b",
      "locator": "Community reference giving the timestamp of 1231006505, the coinbase headline text, the unspendable 50 bitcoin reward and its cause, the extra leading zeros in the hash, the six-day gap to block 1, and that block 0 references no previous block.",
      "recordId": "source-d2c36e64f08016f8",
      "version": null
    },
    {
      "id": "blockstream-block-0",
      "label": "Block 0 (machine-readable block record)",
      "publisher": "Blockstream explorer API",
      "url": "https://blockstream.info/api/block/000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f",
      "note": "Reports block 0 as height 0, version 1, timestamp 1231006505, one transaction, size 285 bytes, weight 1140, bits 486604799, nonce 2083236893, difficulty 1.0, with a Merkle root beginning 4a5e1e.",
      "checkedAt": "2026-10-02T14:48:47.657357+00:00",
      "contentSha256": "d890732201b59ac7b00433c76f4d513340edafe549e1714b3528f707e086b52d",
      "locator": "Reports block 0 as height 0, version 1, timestamp 1231006505, one transaction, size 285 bytes, weight 1140, bits 486604799, nonce 2083236893, difficulty 1.0, with a Merkle root beginning 4a5e1e.",
      "recordId": "source-691e2f1a1d0a41de",
      "version": null
    },
    {
      "id": "bip141",
      "label": "BIP141: Segregated Witness (Consensus layer)",
      "publisher": "Bitcoin Improvement Proposals, GitHub",
      "author": "Eric Lombrozo, Johnson Lau and Pieter Wuille",
      "url": "https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0141.mediawiki",
      "note": "Records the earlier 1,000,000-byte limit and defines base size, total size, block weight as base size times three plus total size with a 4,000,000 limit, and virtual size as weight divided by four, rounded up to a whole virtual byte rounded up.",
      "checkedAt": "2026-10-02T15:04:13.421045+00:00",
      "contentSha256": "d72409335872a32494f75e7547589abf4b3b23b6beebe6bc6999c7a84b135e2c",
      "version": "927b6de9915c9262615a6399de51b200f81e5aa4",
      "locator": "Records the earlier 1,000,000-byte limit and defines base size, total size, block weight as base size times three plus total size with a 4,000,000 limit, and virtual size as weight divided by four, rounded up to a whole virtual byte rounded up.",
      "recordId": "source-896e868816ad19d1"
    },
    {
      "id": "bip34",
      "label": "BIP34: Block v2, Height in Coinbase",
      "publisher": "Bitcoin Improvement Proposals, GitHub",
      "author": "Gavin Andresen",
      "issued": "2012-07-06",
      "url": "https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0034.mediawiki",
      "note": "Requires the block height as the first item in the coinbase script for version 2 blocks, to enforce uniqueness, and records block 227,835 on 24 March 2013 as the last version 1 block.",
      "checkedAt": "2026-10-02T15:04:17.161207+00:00",
      "contentSha256": "592c4956dfeedb369f995c51ebc225df4711929a0096d349300b99ef84d1f809",
      "version": "927b6de9915c9262615a6399de51b200f81e5aa4",
      "locator": "Requires the block height as the first item in the coinbase script for version 2 blocks, to enforce uniqueness, and records block 227,835 on 24 March 2013 as the last version 1 block.",
      "recordId": "source-138d653a48233984"
    }
  ],
  "related": {
    "articles": [
      "genesis-block-explained",
      "what-is-a-blockchain",
      "segwit-explained",
      "bitcoin-transaction-fees-and-mempool",
      "how-to-read-a-block-explorer"
    ],
    "dossiers": [
      "how-bitcoin-blockchain-works",
      "bitcoin-block-size-war"
    ],
    "wallets": [
      "genesis-block-coinbase-block-0",
      "patoshi-pattern-early-mining-set-2009-2010"
    ]
  },
  "revisionHistory": [
    {
      "date": "2026-09-23",
      "kind": "published",
      "summary": "Initial Bitcoin encyclopedia entry at this permanent URL."
    },
    {
      "date": "2026-10-02",
      "kind": "correction",
      "summary": "Corrected scope or wording: weight divided by four Corrected scope or wording: rounded up to a whole virtual byte, rounded up"
    },
    {
      "date": "2026-10-02",
      "kind": "publishing-format",
      "summary": "Added reusable claims, explicit source locators, and matching Markdown and JSON. This publishing change does not itself establish factual verification."
    }
  ],
  "citation": "Degrees of Satoshi editorial project. “Anatomy of a Bitcoin block: the header, the coinbase and the weight limit, using block 0.” Published 2026-09-23; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/anatomy-of-a-bitcoin-block/"
}