 So, the Hyperledger Explorer is a tool created to work in conjunction with the fabric network. It gives the user an ability to see into the permission ledger and view any of the blocks and transactions that have been created. Also you have the ability to view and invoke and deploy any of the chain code associated with the network. It's pretty good with giving a more realistic view instead of having just the theory of what's going on on the blockchain. You can see all of the parts that are comprised in the network and you can view multiple networks on our Explorer. Currently the Explorer is in the version 1.15. We released that around April of this year. We support all of the latest technologies and we're supporting versions 1.4 and 2.3 for the Hyperledger fabric. We have a branch already there in Alpha release for the Hyperledger Aroha integration and we also support a Docker image to make it easier for anyone who would like to stand up the network. So we allow this application on the client side to be deployed in three different ways. You can have it standalone, you can have it as a Docker container which I just discussed and you can have it deployed in clusters like in AWS. We have a couple more notes about it. So currently the top contributors to the Explorer in our community is DTCC. We have teams in the US and in India and we also have Fujitsu which is also contributing to the overall Explorer. We submitted proposals to get out of incubation around December of 2019 and earned our CWI badge in November 2019. So just to get into more details on the features of the Explorer, we're going to have a demo to show standing up a network and actually seeing it on the page and all of the steps in between but a quick overview would just go through the features that are most important. Our blockchain has the typical stand-ups where you have transactions and blocks and nodes and chain codes and we allow on the dashboard you can easily see how much blocks are associated with a particular network, the transactions that are also associated and how much nodes are active on the network. We allow you to sync up to more than one network so if you had to manage a cluster of different networks you could easily switch tabs and change the view to see what is going on on that network at a live moment. We have different graphs to show the transaction and block activity whether you want to chop it down to how much blocks have been coming in in the last hour and how much blocks are happening per minute. We also have a feature where you can see the latest block on the chain as well as we can view the chain codes associated with any transactions that are currently coming in. It dynamically discovers any new channels and we allow for it to switch the data presentation up at the top and you get real-time notifications for any new blocks so if you are already logged in on the application, if someone submits another block or any more transactions, you get a notification in real-time and it has a good amount of user management functionalities so you can add users who are allowed to either come in as an admin or just view the same client-based. So for the application so far, we have some next plan, what we are working on and what we want to add. We have the endorsement policy is something that we are going to look more into and exposing the metrics as per each peer via Prometheus. We want to eventually raise up the explorer so that you can see the next level ledger data and query the platform and you can track any historical operations that have happened against the chain and give it a better view for data analytics. So if you want to analyze the schema on the ledger, you can go ahead and do so. So right now, we are going to have Anil who is going to show what the application looks like right now and a quick demo going through standing up your own personal fabric network and then having it sync up to the explorer. Yeah, thanks, Mikia. So I'll start sharing my screen and go over the demo. So let me know once you're able to see my screen. Are you able to see my screen? You can see it. Yeah, so this demo has two parts to it. One is the setup of the sample fabric network and the setup of the explorer part of it. So is the sample fabric that we are going to show in the demo will contain two peer nodes and an order of node and yeah, let's get started with that. Okay. So we start with downloading the downloading a sample fabric script. So this scripts, it contains scripts to actually start a start a fabric network with the two peer nodes and an order of node. So it's a sample network that gets started by running that description. So we're downloading that script now. So after that, we use this girl command to actually download the fabric, Docker fabric images, the binaries as well as the conflict files. Yeah, so that's what is happening now. So after this is done, so after this is done, we use the sample script that I spoke about, we run the command for network does it not a search to actually start up the fabric sample fabric network with two peer nodes and an order of node and we use the option create channel to start the network and create a channel also. Okay. So the channel is, I mean, the network got started and the channel got created. So we can use this Docker PS command to see the status. So this shows three fabric images each representing API node. So for example, you can see that there is org one node, there's org two node and there's order. So there are three nodes, which are up and running at the moment. So after we have started the sample test network, we are ready to deploy a chain code. So we use the deploy CC command to actually deploy a chain code for this sample network. And then after we deploy it, we are ready to invoke the chain code that we just deployed. So here we are invoking the chain code. So whatever environmental ways they need to be set up to invoke the chain code, we did that there. Now, with this, we are done with the fabric part of the setup. Now let's move on to the Explorer part. So we start that by downloading the report using the control command, we download the report and one thing that I want to mention here is that this particular setup is such that the fabric nodes as well as the Explorer are hosted on the same server. So it's a local, it's a local setup basically. And so the Explorer part, we begin by installing the API of the backend components. We do that here, we are installing the backend components. After we install the backend components, we install the web components or the front-end components. Yeah, we are installing the front-end components. After which we are going to build the web app, web components. And one more thing is that here even in the Explorer also, the same server is serving both the API as well as the web part. So it's the same, it's one server acting as both API server and web server. And here we are building the web component, yeah. So once we are done with the installation part, what we do next is we make some changes to the config files of the Explorer so that this Explorer is able to point to the sample fabric network that we just started in the previous step. So here we have a file called first-network.json where we go and reference the full path of the peer nodes. So we make changes to it to the full path so that it is able to connect to the network that we just created. So once this is done, the next step, what we do is we run a database script. So what this database script does is that it creates a Postgres SQL DB, it does that and then it uses that connection profile from previous step to connect to the sample network, pull all the data from the sample network and put it in this, the DB that, Postgres DB that got created. So it's running the DB script right now. So after this script is complete, we will have a DB called fabric explorer which will be created, which will contain the fabric network data. So you can see that the fabric explorer DB has been created. So with this, our setup part is done. So our setup part of the Explorer is done. Now what we do is we start the server which is going to serve both the API and the web. So we're going to start that server. After we do that, we are all set and we are ready to launch our browser and start looking at the network data. So we select the network, we enter our credentials, our app is ready to be built out. So we log in and this, as you can see, this is the user interface of our Explorer. So it contains different tabs. So the dashboard is the home tab. So this contains all the summary of information of the network, the number of blocks, transactions, nodes, chain codes, everything. And then we have the network tab, the list of peer nodes and other details related to each peer and then blocks. So the list of blocks present in that and the number of, the list of transactions present in the network, all that information is present in different tabs here, chain codes, the channels, everything. So next what we are going to do is we are going to invoke a set of chain codes so that transactions get created and blocks get added to the, to the fabric network. So we are just running a sample command from one to 100. So it's invoking chain code and the same that, this is the invoking of the chain code and transactions, everything gets reflected on the user interface. So this is how it will look as you can see the transactions and the blocks are increasing as and when the changes happen in the network, it gets reflected here. So in all the tabs, we can see that the changes happening in the network is getting reflected. Yeah. I think, yeah, that's pretty much it actually with that demo. So I want to stop sharing. If there are any questions, you can go ahead and ask this question. So I think we have a question from Shane saying, is there an interface to see private data collections? So I just wanted to clarify, are you meaning like between a private network itself or on the blockchain network that's there or because currently the net is private, as long as the person standing up in that work has the keys, then they could display any of the nodes or blocks, transactions. Yeah. So you can see private data collections. Is there any other questions? So let me show you. If anyone has any further questions and they want to either get the blockchain explorer for their own personal use, you could get to our GitHub link we've listed in the slides. You can also see the Docker image and we have documentation that goes through standing up and maintaining anything dealing with the blockchain explorer. We are on rocket chat. The community is there and anyone who has questions, troubleshooting, they just ask the question into the chat and there's always someone who will respond back whether it's one of the moderators on our side and the developers or one of the people who use the explorer on their end always willing to help. I think we'll see if we're good on time. We can ask a couple more questions if you guys have any. I think that's pretty much it, Rikia. Okay. So yeah. All right. Thank you. Thank you. It's been a pleasure. Thanks for joining our demo.