Allocation Details Page
A page showing the details of an allocation
Last updated
A page showing the details of an allocation
Last updated
You can access this page by one the following:
Click on any clickable Allocation ID, for example, in the allocations table in the Wallet Details Page.
Use the URL to: https://atlus.cloud/allocation-details/<allocation_id>
This page shows details about the allocation. The Allocation is a contract of storage between the client and the system, based on which some storage space is dedicated for the client's data. More information about the allocation can be found in the Allocation documentation.
This page consists mainly of one section:
This section views the details of the allocation in JSON format, with an overview of the most important information
This part shows the most important information about the allocation, which are:
Details Key | Description |
---|---|
Hash | This is the hash of the allocation, which is also its identifier, with a copy icon to copy it to the clipboard. |
Owner | This is the address of the wallet of the owner of the allocation, which is also the client ID of the owner, with a copy icon to copy it to the clipboard. Clicking on this redirects to the Wallet Details Page of this client. |
Transaction | This is the hash of the "New Allocation" transaction via which this transaction was created. with a copy icon to copy it to the clipboard. Clicking on this redirects to the Transaction Details page of this transaction. |
Size | This is the maximum storage space of this allocation. |
Data Shards | This is the count of data shards involving in this allocation. Data shards count decides how many blobbers that the allocation data will be split among. |
Parity Shards | This is the count of parity shards involving in this allocation. Parity shards are replicas of the data shards that are used for data protection and fault tolerance. This count also decides how many blobbers will involve in carrying those parity shards. |
Write Pool | This is the amount of ZCN locked by the owner of this transaction to cover the expenses of the owner's write operations on this allocation. More information about the Write Pool in the Token Pools documentation. |
Expiration Date | This is when the allocation will expire, meaning it will not be able to receive more data of the client. |
This part of the section shows the JSON format of the details of this allocation. More information about the allocation data can be found in The Allocation Entity page.