> For the complete documentation index, see [llms.txt](https://gitbook-docs.coinmetrics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-docs.coinmetrics.io/network-data/atlas-overview/accounts.md). # Accounts /blockchain-v2/{asset}/accounts The **Account** endpoint returns a list of accounts, which have the following fields: | Field | Description | | --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | account | [Account](/network-data/atlas-overview/accounts.md) as described in the Atlas overview | | type | Account type (UTXO, Virtual, Account) | | balance | Current account balance in native units | | n\_debits | Number of debits | | n\_credits | Number of credits | | creation\_height | Block height at creation of account | | creation\_block\_hash | Block hash at creation of account | | creation\_time | Block time at creation of account | | creation\_chain\_sequence\_number | The positioning of the account creation transaction relative to all other transactions that have taken place on this chain | | last\_chain\_sequence\_number | The positioning of the last transaction that took place for this account relative to all other transactions that have taken place on this chain | | last\_debit\_height | Block height of the last debit | | last\_credit\_height | Block height of the last credit | | denomination | The denomination of the balance update. Only present for assets that support multiple denominations, and only when the denomination differs from the asset's default. See [Multi-Denomination Assets](/network-data/atlas-overview/balance-updates.md#multi-denomination-assets). | ## Multi-Denomination Assets Certain Atlas assets track activity across many independent sub-tokens rather than a single fixed denomination. For these assets, the `denomination` field in each balance update identifies the specific sub-token the update applies to. The sub-token is identified by its contract address. When `denomination` is absent from a balance update, the update's denomination is the asset's default (its symbol, e.g. `btc`). ### Morpho Vault Assets Morpho Vault assets (`MORPHO_VAULTS_ETH`, `MORPHO_VAULTS_BASE`, `MORPHO_VAULTS_ARB`, `MORPHO_VAULTS_AVAXC`, `MORPHO_VAULTS_OP`) aggregate ERC-4626 vault token activity across all MetaMorpho vaults deployed on the respective chain. Each vault is an independent ERC-20 token with its own contract address and decimal precision. For these assets: * The `denomination` field contains the vault's contract address as a lowercase 40-character hex string (no `0x` prefix). * The `balance` fields are expressed in the vault's own share token units (scaled by that vault's decimals). * Balances across different denominations are not directly comparable because each vault's share token represents a different underlying asset. **Example:** The steakUSDC vault on Ethereum (`0xBEEF01735c132Ada46AA9aA4c54623cAA92A64CB`) appears as denomination `beef01735c132ada46aa9aa4c54623caa92a64cb` in balance updates for `MORPHO_VAULTS_ETH`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://gitbook-docs.coinmetrics.io/network-data/atlas-overview/accounts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.