Using the Block Explorer
All blocks and transactions on the Decred blockchain are visible through the use of the block explorer, dcrdata.
Public instances of dcrdata are available for the following networks:
Blocks can be found by searching for their block height number, clicking on a
Height value from the home page, or from their
BlockHash value. Older
blocks will have lower block numbers.
Each block is packed with information. There are two main sections inside a block:
- The Block Header
- This shows summary information about this specific block, as well as a link to the previous block in the chain.
- Consisting of:
- The Proof-of-Work reward
- The Treasury reward
- Proof-of-Stake votes and rewards
- Proof-of-Stake ticket purchases
- All other regular transactions which transmit DCR across the network
- Consisting of:
The following table should help explain what you’ll see in the top section of dcrdata. This is generally all information that’s also found inside a block header, although it adds some additional context.
For a more advanced description of block headers, see the Dev Docs on Block Header Specifications.
||The unique hash of this specific block, which was found by the miner.|
||The number of new blocks which follow this block in the chain.|
||The size of the block (in kB).|
||The height of the blockchain in which this block resides.|
||The version of the block header.|
||A hash value of all the transaction hashes and stake hashes (ticket purchases, votes, and revocations) included in this block.|
||Originally, this was a hash value of all the stake related transaction hashes in this block. However, as of DCP-0005, the stake hashes were moved into the Merkle Root, and the Stake Root was repurposed to house header commitments. These includes additional proofs and compact filters, which enable a more secure SPV mode for lightweight clients.|
||The number of regular transactions (DCR sent from one user to another).|
||The amount of new DCR minted in this block.|
||The time this block was created by a miner and was included in the blockchain.|
||The value used by a miner to find a valid solution for this block.|
||Used to signify the voting result on the previous block. This will either be 0 or 1. If 1, the previous block was approved by proof-of-stake voters. If 0, the previous block was disapproved by proof-of-stake voters and all non-stake transactions in the block were invalidated, including the newly generated block reward for the proof-of-work miner and the Decred Treasury.|
||The hash value of the final state of the lottery used to determine which tickets were eligible to vote on the previous block, and thus be included in this block. It consists of the five winning ticket hashes, as well as the state of the pseudorandom number generator that was used to select those winning tickets from the live tickets pool.|
||The number of successful proof-of-stake votes cast in this block. The maximum value is 5. Tickets can fail to vote when called upon, but a minimum of 3 votes are required.|
||The number of stake ticket purchases in this block, which will be added to the ticket pool.|
||The number of tickets that failed to vote and were revoked.|
||The total number of active proof-of-stake tickets.|
||A compact version of the network difficulty at the time the block was mined.|
||The price of one proof-of-stake ticket.|
||The stake version used for voting on the created block.|
||The proof-of-work network difficulty.|
This section lists all the transactions that were mined into this block. Transactions are chosen from the network mempool in order of highest fee first. All transactions in the block overview follow this order: Standard transactions (peer-to-peer transfer), proof-of-stake votes, proof-of-stake ticket purchases. The following sections will review each type of transaction.
Here’s the information included in standard Decred transactions.
||The size of the transaction in bytes.|
||The rate of fees collected by the network (per kB).|
||The time the network confirmed the transaction.|
||The time a miner included the transaction in a block.|
||The block number that the transaction became a part of.|
Mined Time, and
Included in Block will not have a value until a miner validates the transaction and includes it in a Decred block. After being confirmed in a block, the transaction is considered complete.
For a ticket purchase (stake submission) there are a few differences from a standard transaction shown.
Note the difference under details: The word
Ticket appears above the
sender’s wallet address on the left, and the words
Commitment appear on the right. This particular user purchased a
stake ticket for 8.75411638 DCR and received change in the amount
of 7.15994209 DCR. The address listed on the left under
the address that contains the funds used to purchase this
ticket. The first output on the right is the address that retains
voting rights for this specific ticket. The second output,
Commitment, is the address where the reward will go. This is not yet
shown by the block explorer at this time. The third and final output
is the address where change for this transaction will be sent.
Note the identifying terms in the details section:
Block Commitment, and
These keywords indicate that this transaction is a vote that was cast from a proof-of-stake ticket holder. In this particular example, the user had previously purchased a ticket for 8.99472311 DCR and was sent 10.82959184 DCR after the vote was cast in this transaction.