Difference between revisions of "Block Explorer"
Todd Price (talk | contribs) |
|||
| (10 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | A Block Explorer is an application that allows users to view and query data stored on the BitcoinSV ledger and network. Typically accessed through a web browser, Block Explorers allow users to view details of Bitcoin [[Block|blocks]], [[transactions]] and [[Address|addresses]]. Their primary function is to allow users to track network activity in real-time. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | A Block Explorer is an application that allows users to view and query data stored on the BitcoinSV ledger and network. Typically accessed through a web browser, Block Explorers allow users to view details of Bitcoin [[Block|blocks]], [[ | ||
==Structure== | ==Structure== | ||
| − | The structure of a typical | + | The structure of a typical Block Explorer is to have a mining client with a front end that pulls data from its own copy of the [[blockchain]] and presents it to users through a web interface. |
| − | In future it is expected that | + | In future it is expected that Block Explorers will develop their own tooling and client that can detect additional information that is not typically monitored by a mining client such as the emergence of a block race, transactions which the node is not set up to validate and more. |
| − | Real time information on both blocks and transactions is typically provided. | + | Real time information on both blocks and transactions is typically provided in addition to other information such as the history of a given Bitcoin address or a list of transactions containing particular [[metadata]]. |
===Block information=== | ===Block information=== | ||
| Line 25: | Line 13: | ||
*'''Age:''' Elapsed time between now and the timestamp that indicates when the block was discovered | *'''Age:''' Elapsed time between now and the timestamp that indicates when the block was discovered | ||
*'''Transaction Count:''' number of transactions included in the block | *'''Transaction Count:''' number of transactions included in the block | ||
| − | *'''Fees:''' Aggregate value of all [[Transaction fees]] paid to the | + | *'''Fees:''' Aggregate value of all [[Transaction fees]] paid to the Miner by users |
| − | *'''Reward:''' Total | + | *'''Reward:''' Total Miner reward including transaction fees and [[block subsidy]] |
| − | *'''Mined by:''' Identity of the | + | *'''Mined by:''' Identity of the Miner or mining pool whose node mined this block |
*'''Size:''' Size of the block as obtained by adding the sizes of each transactions included in the block | *'''Size:''' Size of the block as obtained by adding the sizes of each transactions included in the block | ||
===Real time Transaction information=== | ===Real time Transaction information=== | ||
| − | In addition the | + | In addition, the Block Explorer provides a full set of information regarding transactions that have either been mined into a block, or accepted into the Block Explorer's node client's mempool. |
*'''[[Block]]:''' The hash of the block in which the transaction was mined (if the transaction has not yet been mined, the confirmation field is typically not shown) | *'''[[Block]]:''' The hash of the block in which the transaction was mined (if the transaction has not yet been mined, the confirmation field is typically not shown) | ||
| Line 41: | Line 29: | ||
*'''[[Transaction fees|Fee Paid]]:''' The total transaction fee paid by the spending party | *'''[[Transaction fees|Fee Paid]]:''' The total transaction fee paid by the spending party | ||
*'''Fee Rate:''' The transaction fees paid by the spending party as a ratio of Satoshis/Byte which is the total fee paid divided by the size of the transaction | *'''Fee Rate:''' The transaction fees paid by the spending party as a ratio of Satoshis/Byte which is the total fee paid divided by the size of the transaction | ||
| + | *'''[[Coinbase|Coinbase data]]:''' If the transaction is the coinbase transaction of a block, the explorer will typically show the coinbase text that the Miner has embedded in the transaction | ||
| + | |||
| + | In addition to these fields, the explorer will usually include other information about the transaction including the number of inputs and outputs, the values of those inputs and outputs, the scripts used to spend the inputs, and the new scripts created in the outputs. Most explorers will also offer the user different ways to view this information such as raw hex, interpreted Bitcoin script or in [[wikipedia:JSON|JSON]] format. | ||
==Searchable Information== | ==Searchable Information== | ||
| − | The main function of | + | The main function of Block Explorers is to allow users to search for data in the Bitcoin ledger and [[blockchain]]. This is typically performed using a search tool. |
Typical search functions include: | Typical search functions include: | ||
| Line 53: | Line 44: | ||
* Transaction metadata | * Transaction metadata | ||
| − | Typically, the explorer responds to a search with a page containing all the details about the subject of a search request. | + | Typically, the explorer responds to a search with a page containing all the details about the subject of a search request. |
| − | + | ==List of BitcoinSV explorers== | |
| + | * https://whatsonchain.com | ||
| + | * https://bitcoinblocks.live | ||
| + | * https://blockchair.com | ||
| + | * https://coin.dance | ||
| − | + | ==Attribution== | |
| − | + | This content is based on content sourced from https://en.bitcoin.it/wiki/Block_chain_browser under [https://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution 3.0]. Although it may have been extensively revised and updated, we acknowledge the original authors. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 05:49, 25 April 2022
A Block Explorer is an application that allows users to view and query data stored on the BitcoinSV ledger and network. Typically accessed through a web browser, Block Explorers allow users to view details of Bitcoin blocks, transactions and addresses. Their primary function is to allow users to track network activity in real-time.
Structure
The structure of a typical Block Explorer is to have a mining client with a front end that pulls data from its own copy of the blockchain and presents it to users through a web interface.
In future it is expected that Block Explorers will develop their own tooling and client that can detect additional information that is not typically monitored by a mining client such as the emergence of a block race, transactions which the node is not set up to validate and more.
Real time information on both blocks and transactions is typically provided in addition to other information such as the history of a given Bitcoin address or a list of transactions containing particular metadata.
Block information
The explorer provides data on all blocks that have been added to the ledger, and are usually updated within seconds of a valid block being discovered. This data shows:
- Block height: Number of blocks since the Bitcoin Genesis block was mined
- Age: Elapsed time between now and the timestamp that indicates when the block was discovered
- Transaction Count: number of transactions included in the block
- Fees: Aggregate value of all Transaction fees paid to the Miner by users
- Reward: Total Miner reward including transaction fees and block subsidy
- Mined by: Identity of the Miner or mining pool whose node mined this block
- Size: Size of the block as obtained by adding the sizes of each transactions included in the block
Real time Transaction information
In addition, the Block Explorer provides a full set of information regarding transactions that have either been mined into a block, or accepted into the Block Explorer's node client's mempool.
- Block: The hash of the block in which the transaction was mined (if the transaction has not yet been mined, the confirmation field is typically not shown)
- Status: If a transaction isn't mined, this field may show the transaction as Unconfirmed
- Timestamp: The timestamp in the block header in which this transaction was mined (if the transaction has not yet been mined, the timestamp field is typically not shown)
- Version: The version of the protocol against which this transaction is to be validated
- Size: The size of the serialised transaction in bytes
- Confirmations: The number of blocks mined on top of the block containing the transaction (if the transaction has not yet been mined, the confirmation field is typically not shown)
- Fee Paid: The total transaction fee paid by the spending party
- Fee Rate: The transaction fees paid by the spending party as a ratio of Satoshis/Byte which is the total fee paid divided by the size of the transaction
- Coinbase data: If the transaction is the coinbase transaction of a block, the explorer will typically show the coinbase text that the Miner has embedded in the transaction
In addition to these fields, the explorer will usually include other information about the transaction including the number of inputs and outputs, the values of those inputs and outputs, the scripts used to spend the inputs, and the new scripts created in the outputs. Most explorers will also offer the user different ways to view this information such as raw hex, interpreted Bitcoin script or in JSON format.
Searchable Information
The main function of Block Explorers is to allow users to search for data in the Bitcoin ledger and blockchain. This is typically performed using a search tool.
Typical search functions include:
- Transaction hash or TXID
- Block height
- Block hash
- Bitcoin address
- Transaction metadata
Typically, the explorer responds to a search with a page containing all the details about the subject of a search request.
List of BitcoinSV explorers
Attribution
This content is based on content sourced from https://en.bitcoin.it/wiki/Block_chain_browser under Creative Commons Attribution 3.0. Although it may have been extensively revised and updated, we acknowledge the original authors.