You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/2_architecture/components/6_explorer.md
+52-10Lines changed: 52 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,27 +6,69 @@ The Explorer keeps track of [Aligned Service Manager](./3_service_manager_contra
6
6
7
7
It has an internal state of previous batches, actively listens for new batches and their responses. The Explorer then displays this information for Users to visualize the submitted batches, their states and more useful information in real time.
8
8
9
-
In the landing page we can see information such as how many [Operators](./4_operator.md) are currently registered and running, how many Batches and how many total Proofs have been verified.
9
+
In the landing page,
10
+
we can see information such as how many [Operators](./4_operator.md) are currently registered and active,
11
+
total ETH restaked by said Operators, how many Batches and how many total Proofs have been verified.
10
12
11
-
13
+
The main Aligned contracts such as the Aligned Service Manager or the Batcher Payment Service are easily accessible
14
+
from the Explorer with links to etherscan.
12
15
13
-
From here, we can search for a specific batch by its Merkle Root, we can directly jump to any one of the last 5 submitted batches, and we can easily go to the `Latest Batches` page, where we can navigate through the various pages of batches of proofs submitted to aligned, ordered by latest submission, and easily check their on-chain status, timestamp, and block number.
16
+
14
17
15
-
18
+
From here, we can search for a specific batch by its Merkle Root or even find a batch, or if you want to find which batch contains a specific proof, you can also search by proof hash.
19
+
We can also directly jump to any one of the last 5 submitted batches, and we can easily go to the `Batches` page,
20
+
where we can navigate through the various pages of batches of proofs submitted to aligned, ordered by latest submission,
21
+
and easily check their on-chain status, timestamp, and block number.
16
22
17
-
From there we can also click any individual batch Merkle Root to view its details.
23
+
18
24
19
-
From here we can visualize:
25
+
We can also click any individual batch hash to view its details.
20
26
21
-
- the whole `Merkle Root`
22
-
-`Amount of Proofs` in the batch
27
+
From the details view, we can visualize:
28
+
29
+
- The `Batch Hash` Merkle Root and a copy to clipboard button
30
+
- The batch's `Status`, either `Pending` or `Verified`
31
+
-`Batcher Sender Address` which is the address of the batcher that submitted the batch
32
+
-`Number of Proofs in this Batch`, the number of proofs included in the batch
33
+
-`Fee per Proof`, fee paid per proof in the batch in ETH and USD
34
+
-`Proofs in the Batch`, which when pressed will show a list of all the proof hashes included in the batch
23
35
- Ethereum's `Submission Block Number`, linked to etherscan
24
36
-`Submission Transaction Hash`, linked to etherscan
25
37
-`Submission Timestamp` of the batch
26
-
-`Status`, either `Pending` or `Verified`
27
38
- Ethereum's `Response Block Number`, linked to etherscan
28
39
-`Response Transaction Hash`, linked to etherscan
29
40
-`Response Timestamp` of the batch
41
+
- Lastly, if the batch is `Verified`, we can see a small X Post button that lets us easily share on X that the batch has been verified.
42
+
43
+
44
+
45
+
The `Operators` page shows a list of all registered operators,
46
+
their restake concentration in %, the total amount of ETH they have restaked and their status.
47
+
48
+
These are ordered by the amount of ETH restaked, with the top operator being the one with the most ETH restaked.
49
+
50
+
When hovering over an operator, we can see the operator's address and id.
51
+
52
+
53
+
54
+
The `Operator Details` page shows the operator's id, address, total ETH restaked,
55
+
restake concentration in %, and the assets restaked order by the amount of ETH restaked.
56
+
57
+
The Operators image is also displayed, and we access other information the operator chose to share, such as their
58
+
website, X, and EigenLayer dashboard profile for more details.
59
+
60
+
61
+
62
+
The `Restake` page can be accessed by clicking the `Total Restaked` call-to-action button on either the landing page or
63
+
the operators' page.
64
+
65
+
Here we can see the various assets that can be restaked, and the amount of ETH restaked in each asset.
66
+
67
+
The table is ordered by the amount of ETH restaked, with the top asset being the one with the most ETH restaked.
68
+
69
+
30
70
31
-
71
+
The `Restake Details` page shows the asset's name,
72
+
symbol, total ETH restaked, Strategy Address and Token Address both linked to etherscan.
32
73
74
+
0 commit comments