> For the complete documentation index, see [llms.txt](https://docs.decenomy.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decenomy.net/tutorials/decenomy-explorer/explorer-api.md).

# Explorer API

This documentation is intended to provide information on the available methods to extract data from DECENOMY Explorer using its API.

Being a public API, there is no need to use any kind of authentication.

\
[<mark style="color:blue;">API v1</mark>](#api-v1-endpoint-url) reports plain text.\
\
[<mark style="color:blue;">API v2</mark>](#api-v2-endpoint-url) reports more info in detail.

## API v1 Endpoint URL

<mark style="color:blue;"><https://explorer.decenomy.net/api/v1/coins/></mark><mark style="color:orange;">coin</mark><mark style="color:blue;">/</mark>

### Path parameters v1

<table><thead><tr><th width="175">Name</th><th width="98" align="center">Type</th><th width="334">Description</th><th>Info</th></tr></thead><tbody><tr><td>coin</td><td align="center">string</td><td>should be replaced by the coin ticker, always in caps</td><td>Required</td></tr></tbody></table>

### Query parameters v1

<table><thead><tr><th width="176">Name</th><th width="94" align="center">Type</th><th width="337">Description</th><th>Info</th></tr></thead><tbody><tr><td>getblockcount</td><td align="center">string</td><td>Plain block count, just the block number value</td><td>Optional</td></tr><tr><td>getmoneysupply</td><td align="center">string</td><td>Circulating supply - It will output just the number value of the total supply minus the locked supply</td><td>Optional</td></tr><tr><td>getlockedsupply</td><td align="center">string</td><td>Locked supply - It will output just the number value of the locked/burned supply</td><td>Optional</td></tr><tr><td>gettotalsupply</td><td align="center">string</td><td>Total supply - It will output just the number value of the circulation supply plus the locked supply</td><td>Optional</td></tr></tbody></table>

### Example query v1

```
https://explorer.decenomy.net/api/v1/coins/SAPP/getblockcount
```

### Example response v1

```
1987842
```

## API v2 Endpoint URL

<mark style="color:blue;"><https://explorer.decenomy.net/api/v2/></mark><mark style="color:orange;">coin</mark><mark style="color:blue;">/</mark>

### Path parameters v2

<table><thead><tr><th width="164">Name</th><th width="124" align="center">Type</th><th width="355">Description</th><th align="center">Info</th></tr></thead><tbody><tr><td>coin</td><td align="center">string</td><td>should be replaced by the coin ticker, always in caps</td><td align="center">Required</td></tr></tbody></table>

### Query parameters v2

<table><thead><tr><th width="163">Name</th><th width="122" align="center">Type</th><th width="355">Description</th><th>Info</th></tr></thead><tbody><tr><td>blocks</td><td align="center">string</td><td>Last 30 blocks - blockhash tx /<br>/ blocktime / height / confirmations</td><td>Optional</td></tr><tr><td>transactions</td><td align="center">string</td><td>Last 30 blocks - blockhash / blocktime / height / tx /<br>confirmations / recipients / amount</td><td>Optional</td></tr><tr><td>peers</td><td align="center">string</td><td>Full information of peers available</td><td>Optional</td></tr><tr><td>masternodes</td><td align="center">string</td><td>Full information of each masternode in the network</td><td>Optional</td></tr><tr><td>info</td><td align="center">string</td><td>Wallet and blockchain information</td><td>Optional</td></tr><tr><td>masternode/count</td><td align="center">string</td><td>Total number of masternodes connected in the network</td><td>Optional</td></tr><tr><td>status</td><td align="center">string</td><td>Status of blockchain based in last block received</td><td>Optional</td></tr><tr><td>burnaddresses</td><td align="center">string</td><td>Burn address Information</td><td>Optional</td></tr></tbody></table>

### Example query v2

```
https://explorer.decenomy.net/api/v2/SAPP/info
```

### Example response v2

```
{
  "response": {
    "connections": 171,
    "errors": "",
    "blocks": 1987846,
    "paytxfee": 0,
    "moneysupply": 1224915018.8013475,
    "difficulty": 527924.3523641471,
    "keypoolsize": 100,
    "keypoololdest": 1627317470,
    "walletversion": 169900,
    "timeoffset": 0,
    "testnet": false,
    "version": 1050100,
    "staking status": "Staking Inactive",
    "protocolversion": 70931,
    "services": "NETWORK/BLOOM/",
    "balance": 0,
    "relayfee": 0.0001,
    "proxy": ""
  },
  "success": true
}
```


---

# 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://docs.decenomy.net/tutorials/decenomy-explorer/explorer-api.md?ask=<question>&goal=<user_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.