<p>All of the transaction history is communicated between peers over a binary <a href="https://en.bitcoin.it/wiki/Protocol_documentation" rel="noreferrer">gossip protocol</a>. You can request specific blocks, sequences of blocks, or specific transactions, and clients will normally communicate by broadcasting all of the information they receive to other peers they are connected to - enabling each client to stay mostly up-to-date once they've downloaded the historical ledger. It is required that you connect to multiple peers to request information so that you are sure to get up-to-date information if a potentially malicious peer tries to withold information.</p>

<p>If you are already running a full node (which is a software client which uses the above protocol and stores the valid information it receives), then you already have the transaction history on your machine running the software. For Bitcoin Core, the files are stored in the <code>./store/blocks/</code> subdirectory of bitcoin's storage directory. The directory contains many files named blkXXXXX.dat, which are serialized sequences of blocks. Each file contains many <a href="https://en.bitcoin.it/wiki/Block" rel="noreferrer"><code>Block File</code></a> structures in serial, up to a limit of 128MB per file. The files are numbered ascendingly, with blk00000.dat being the oldest containing the genesis block as its first <code>Block File</code>. The <code>Block File</code> structure mimics the structure of the information of a <code>block</code> message received over the message protocol, except is prefixed with a magic number and size of the block.</p>

<p>Typically, if you want to write a block explorer, it would be simpler to read the information from the block files stored by Bitcoin Core, unless you need your block explorer to contain live information, in which case you will need to get information over the gossip protocol directly, or through Bitcoin Core's ZMQ interface, because the node software only commits confirmed transactions into block files.</p>

CC BY-SA 4.0
2019-02-11T22:47:10.043Z
2019-02-11T22:47:10.043Z
Mark H
<p>I have read that the blockchain is a public ledger with all transactions of a decentralized community, furthermore i read that everyone can check that ledger for transactions that happened within the network. My question is how i am able to look into the blockchain to check for transactions without using sites like blockchain.info. </p>

CC BY-SA 4.0
2019-02-11T22:07:04.553Z
Are you referring to transactions or trades on an exchange?
JBaczuk
CC BY-SA 4.0
2019-02-12T21:49:54.993Z
No what I meant is how and where I can get the same data like you can see on sites like blockchain.info show.
Иосиф Виссарионович Сталин
CC BY-SA 4.0
2019-02-27T15:22:32.330Z
It would be better to specify the blockchain platform that you're referring to. For example, Bitcoin blockchain, as the blockchain is referred to as a "data structure", while the Bitcoin is referred to as a "protocol" that uses the blockchain. Each blockchain platform may have different behavior and features depending on whether blockchain-based protocol is public permission-less or private permissioned etc. Briefly blockchain does not include necessarily all of Bitcoin features such as **transparency** etc.
Questioner
<blockchain><blockchain.info><historical-trade-data>
How can i look into the Blockchain
Иосиф Виссарионович Сталин
# How can i look into the Blockchain

(Asked by: username_0 on 2019-02-11)

I have read that the blockchain is a public ledger with all transactions of a decentralized community, furthermore i read that everyone can check that ledger for transactions that happened within the network. My question is how i am able to look into the blockchain to check for transactions without using sites like blockchain.info.

**Tags:** blockchain, blockchain.info, historical-trade-data

> **Comments:**
> **username_1**: Are you referring to transactions or trades on an exchange?  
> **username_0**: No what I meant is how and where I can get the same data like you can see on sites like blockchain.info show.  
> **username_2**: It would be better to specify the blockchain platform that you're referring to. For example, Bitcoin blockchain, as the blockchain is referred to as a "data structure", while the Bitcoin is referred to as a "protocol" that uses the blockchain. Each blockchain platform may have different behavior and features depending on whether blockchain-based protocol is public permission-less or private permissioned etc. Briefly blockchain does not include necessarily all of Bitcoin features such as **transparency** etc.  

---

## 1 answers

### Answer by username_3 on 2019-02-11. Score: 5

All of the transaction history is communicated between peers over a binary [gossip protocol](https://en.bitcoin.it/wiki/Protocol_documentation). You can request specific blocks, sequences of blocks, or specific transactions, and clients will normally communicate by broadcasting all of the information they receive to other peers they are connected to - enabling each client to stay mostly up-to-date once they've downloaded the historical ledger. It is required that you connect to multiple peers to request information so that you are sure to get up-to-date information if a potentially malicious peer tries to withold information.

If you are already running a full node (which is a software client which uses the above protocol and stores the valid information it receives), then you already have the transaction history on your machine running the software. For Bitcoin Core, the files are stored in the `./store/blocks/` subdirectory of bitcoin's storage directory. The directory contains many files named blkXXXXX.dat, which are serialized sequences of blocks. Each file contains many [`Block File`](https://en.bitcoin.it/wiki/Block) structures in serial, up to a limit of 128MB per file. The files are numbered ascendingly, with blk00000.dat being the oldest containing the genesis block as its first `Block File`. The `Block File` structure mimics the structure of the information of a `block` message received over the message protocol, except is prefixed with a magic number and size of the block.

Typically, if you want to write a block explorer, it would be simpler to read the information from the block files stored by Bitcoin Core, unless you need your block explorer to contain live information, in which case you will need to get information over the gossip protocol directly, or through Bitcoin Core's ZMQ interface, because the node software only commits confirmed transactions into block files.


---

