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:
Below is a quick review of some of the information on them.
||The block number.|
||How long ago the block was added to the blockchain.|
||The number of transactions included in the block.|
||The number of proof-of-stake votes included in the block.|
||The number of new tickets purchased in this block.|
||The size (in bytes) of the block.|
Latest Transactions, you can see the transaction ID (txid) and
the value (in DCR) transmitted across the network.
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. The top
half of a block overview shows relevant information about this
specific block. This information includes: the block height, the block
hash, and several key network parameters, described below:
||The number of standard transactions (DCR sent from one user to another).|
||The height of the blockchain in which this block resides.|
||The amount of new DCR minted in this block.|
||The time this block was created by a miner and was included in the blockchain.|
||A hash value of all the transaction hashes included in this block.|
||A hash value of all the stake related transaction hashes in this block. This includes ticket purchases, votes, and ticket revocations.|
||(1) Block was approved by proof-of-stake voters. (2) Block was vetoed by proof-of-stake voters and all non-stake transactions in the block were invalidated, along with the newly generated block reward for the proof-of-work miner and the Decred Treasury.|
||The final state of the pseudo random number generator used for ticket selection.|
||The number of successful proof-of-stake votes cast in this block. The maximum value is 5.|
||The number of stake ticket purchases confirmed in this block.|
||The number of tickets that failed to vote and were revoked.|
||The total number of active proof-of-stake tickets.|
||The proof-of-work network difficulty.|
||The price of one proof-of-stake ticket.|
||A compact version of the network difficulty at the time the block was mined.|
||The size of the block (in bytes).|
||The version of the block.|
||The value used by a miner to find the correct solution for this block.|
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.