Depending on the purpose of your monitoring, you will likely need to run one or more Bitcoin full nodes in addition to your monitoring infrastructure. A typical blockchain network includes a set of interconnected nodes that act as peers. These nodes are typically hosted in a local infrastructure, natively configured on a physical machine, or using containerization and virtualization technologies such as Docker and VMware. Transactions submitted to the Bitcoin network are disseminated to all peers, and newly created blocks are propagated, so that all peers have an updated copy of the shared ledger. To better understand the block, its transaction-related events, and associated metadata, we monitor all of our connected peers. To do this, generally use a block browser, which listens to events and provides a visualization of the number of transactions received. , processed and finally regrouped into a new block. However, this level of monitoring does not provide any indication of resource usage on this node, health of other nodes, or latency encountered within the Bitcoin network. Effective monitoring and management of a blockchain network requires a framework that can integrate data, assimilate generated events, and provide efficient visualization of blockchain arrays. This infrastructure must be modular and support deployment topologies, which can allow monitoring at both an individual node and the entire Bitcoin blockchain network.