 Hello, this video will focus on the current state of the blockchain explorer frontend. It shows the running code from the GitHub repository named Iroha2 block explorer web we are looking at right now. I intend to start with the frontend part, demonstrate how things are functioning visually and to switch to the backend after that. Switching between the light and dark themes works nicely. The translations have to be updated after all the detailed pages for blocks, transactions, assets, etc. are ready, because those will add a lot of new text to translate, and short language switching isn't finished yet. The main page is displaying the latest blocks and transactions. The structure we are looking at matches the original design. Transaction filters on the main page don't work yet. Transaction hashes are shortened having a feature display that completely hash would be nice. The block's page is working and it is slightly different compared to the original design. The date and time column turned into the age column. Rows per page switching works, although the direction of a drop-down component requires scrolling and it looks incorrect. It is easy to copy the block hash with the copy button. The assets page differs from the design column wise. The columns are changed, price 24 hour percent, market cap and holders are missing, while the column named total supply was renamed as the total one. The icons on the left are missing. Total values are working and there is a new feature to display store type assets that contain JSON through a number of keys recorded in such an asset. The domain's page is different compared to the original design. There are no dummy icons on the left. The balance result and locked columns are missing. A page for the domain details has to be implemented. The accounts page is only slightly different from the design. The balance column is missing. A functionality to copy the address works nicely. The transaction page is matching the original design. The function details aren't implemented. The filtering logic has to be implemented as well. Currently, it does not work. A block link doesn't have the assigned domain page. Let's have a look at the mobile design. Most of the features are supported and implemented. The only thing I can point out is that the hashes are shortened incorrectly leaving too much space. Now let us review the blockchain explorer backend. It allows the frontend to interact with Iroha, for instance, retrieving the available data. The setup we'll be looking at is using three parts. An Iroha instance, the blockchain explorer backend, and the explorer frontend in development mode that is using a proxy to connect to the backend. It is configured using two files. First, a doting file with a server and mock API configuration in it. Second, a Vita configuration that sets up the proxy to the blockchain explorer backend. Now let's see how the pages work one by one. The blocks page displays a single record and a single page for it. The assets page displays more pages in pagination and more predefined assets as well. The rows per page functionality works normally. Same repeats for other three pages, so we'll look at those briefly. Now, let's query the blockchain explorer backend directly to test it. When we query the API directly, it won't be formatted because formatting takes space. Instead we are going to use HTTP program to debug the API. Let us continue with analyzing the account API route, the important attributes below, such as the page and page size for pagination. Each response will reflect the pagination data we've sent and contains the number of items. When we perform the query, we'll see the asset for given account and account ID, its metadata and rows. The pagination data is reflected in each of the main routes, so let's switch to the assets. Each asset record contains an account ID, a definition ID, its value with a given amount under the C key, its type under the T key. Let us continue with the domains route. Each domain contains the complete account definitions, the complete asset definitions, its ID, its logo, its metadata, a key value store, and its triggers. An individual transaction in the transactions route consists of the data with signatures and a commit marker. The content section contains a hash, a payload with its account, creation time, and a list of instructions. Each transaction signature contains a payload and a public key. An individual block in the block's route contains a block hash key to identify the block. Its height, the amount of rejected transactions, its timestamp, the amount of transactions inside block. If you have questions or suggestions about EROHA Blockchain Explorer, please ask them in the community telegram and discord. Thank you for watching this video. Cheers!