All content has been migrated to docs.dash.org. You will be automatically redirected momentarily.
Under current consensus rules, a block is not valid unless its serialized size is less than or equal to 2 MB. All fields described below are counted towards the serialized size.
|80||block header||block_header||The block header in the format described in the block header section.|
|Varies||txn_count||compactSize uint||The total number of transactions in this block, including the coinbase transaction.|
|Varies||txns||raw transaction||Every transaction in this block, one after another, in raw transaction format. Transactions must appear in the data stream in the same order their TXIDs appeared in the first row of the merkle tree. See the merkle tree section for details.|
The first transaction in a block must be a coinbase transaction which should collect and spend any transaction fee paid by transactions included in this block.
Until the coin limit (~18 million Dash) is hit, all blocks are entitled to receive a block subsidy of newly created Dash value. The newly created value should be spent in the coinbase transaction.
The block subsidy declines by ~7.1% per year until all Dash is mined. Subsidy calculations are performed by the Dash Core GetBlockSubsidy() function.
Together, the transaction fees and block subsidy are called the block reward. A coinbase transaction is invalid if it tries to spend more value than is available from the block reward.
The block reward is divided into three parts: miner, masternode, and superblock. The miner and masternode portions add up to 90% of the block subsidy with the remaining 10% allocated to the governance system.
Dash Core v0.16 included logic to gradually adjust the block reward allocation once the BIP-9 activation threshold was met. The reward reallocation was signaled via BIP-9 bit 5 and was activated at block 1374912 upon signalling by a sufficient number of blocks.
This reallocation will eventually result in miners receiving 40% of the non-governance block subsidy and masternodes receiving 60% of it rather than the 50/50 split that was used for several years.
Reward reallocation changes
Reward reallocation changes began at the first superblock following activation (block 1379128) and then occur every three superblock cycles (approximately once per quarter) until the reallocation is complete.
|Quarter||Block||Miner %||Masternode %||Change (%)|
Updated 7 months ago