# Supported Chains

### Overview

The Nansen API supports 37 blockchain networks across EVM and non-EVM ecosystems. Chain support varies by endpoint.

### EVM Chains

EVM-compatible chains use the standard Ethereum address format (`0x` + 40 hex characters).

| Chain     | Value       | Description           |
| --------- | ----------- | --------------------- |
| Ethereum  | `ethereum`  | Main Ethereum network |
| Arbitrum  | `arbitrum`  | Arbitrum One L2       |
| Avalanche | `avalanche` | Avalanche C-Chain     |
| Base      | `base`      | Coinbase L2           |
| Bitlayer  | `bitlayer`  | Bitcoin L2            |
| BNB Chain | `bnb`       | BNB Smart Chain       |
| Celo      | `celo`      | Celo network          |
| Chiliz    | `chiliz`    | Chiliz Chain          |
| Gravity   | `gravity`   | Gravity network       |
| HyperEVM  | `hyperevm`  | Hyperliquid EVM       |
| IOTA EVM  | `iotaevm`   | IOTA EVM              |
| Linea     | `linea`     | Linea L2              |
| Mantle    | `mantle`    | Mantle L2             |
| Monad     | `monad`     | Monad network         |
| Optimism  | `optimism`  | Optimism L2           |
| Plasma    | `plasma`    | Plasma network        |
| Polygon   | `polygon`   | Polygon PoS           |
| Ronin     | `ronin`     | Ronin sidechain       |
| Scroll    | `scroll`    | Scroll L2             |
| Sei       | `sei`       | Sei EVM               |
| Sonic     | `sonic`     | Sonic network         |
| Unichain  | `unichain`  | Uniswap L2            |
| Viction   | `viction`   | Viction (TomoChain)   |
| zkSync    | `zksync`    | zkSync Era            |

### Non-EVM Chains

Non-EVM chains have unique address formats. See Address Formats for details.

| Chain       | Value         | Description                       |
| ----------- | ------------- | --------------------------------- |
| Algorand    | `algorand`    | Algorand network                  |
| Aptos       | `aptos`       | Aptos network                     |
| Bitcoin     | `bitcoin`     | Bitcoin network                   |
| Hyperliquid | `hyperliquid` | Hyperliquid DEX (perpetuals only) |
| NEAR        | `near`        | NEAR Protocol                     |
| Solana      | `solana`      | Solana network                    |
| Stacks      | `stacks`      | Stacks (Bitcoin L2)               |
| Starknet    | `starknet`    | Starknet L2                       |
| Stellar     | `stellar`     | Stellar network                   |
| SUI         | `sui`         | SUI network                       |
| TON         | `ton`         | The Open Network                  |
| Tron        | `tron`        | Tron network                      |

### Using the "all" Chain

Some endpoints support `"all"` to query across all supported chains:

```json
{
  "chains": ["all"]
}
```

This expands to all chains supported by that specific endpoint.

### Chain Support by Endpoint

Not all chains are available on all endpoints. Here's the support matrix:

#### Smart Money Endpoints

| Chain     | Netflow | DEX Trades | Holdings | Historical |
| --------- | ------- | ---------- | -------- | ---------- |
| ethereum  | Yes     | Yes        | Yes      | Yes        |
| solana    | Yes     | Yes        | Yes      | Yes        |
| base      | Yes     | Yes        | Yes      | Yes        |
| bnb       | Yes     | Yes        | Yes      | Yes        |
| arbitrum  | Yes     | Yes        | Yes      | No         |
| polygon   | Yes     | Yes        | Yes      | No         |
| avalanche | Yes     | Yes        | Yes      | No         |
| optimism  | Yes     | Yes        | Yes      | No         |

#### Token God Mode Endpoints

| Chain    | Flows | Transfers | Holders | PnL |
| -------- | ----- | --------- | ------- | --- |
| ethereum | Yes   | Yes       | Yes     | Yes |
| solana   | Yes   | Yes       | Yes     | Yes |
| base     | Yes   | Yes       | Yes     | Yes |
| bnb      | Yes   | Yes       | Yes     | Yes |
| arbitrum | Yes   | Yes       | Yes     | Yes |
| ton      | Yes   | Yes       | Yes     | No  |
| tron     | Yes   | Yes       | Yes     | No  |

#### Profiler Endpoints

| Chain    | Balance | Transactions | PnL | Related |
| -------- | ------- | ------------ | --- | ------- |
| ethereum | Yes     | Yes          | Yes | Yes     |
| solana   | Yes     | Yes          | Yes | Yes     |
| bitcoin  | Yes     | Yes          | No  | No      |
| ton      | Yes     | Yes          | No  | Yes     |
| tron     | Yes     | Yes          | No  | Yes     |

### Examples

#### Single Chain Query

```json
{
  "chains": ["ethereum"]
}
```

#### Multi-Chain Query

```json
{
  "chains": ["ethereum", "solana", "base"]
}
```

#### All Chains Query

```json
{
  "chains": ["all"]
}
```

### Chain-Specific Considerations

#### Solana

* Uses base58 addresses
* Transaction lookup not supported
* Full support for Smart Money and TGM

#### Bitcoin

* Limited endpoint support (Profiler only)
* Supports P2PKH, P2SH, and Bech32 addresses
* No Smart Money or TGM support

#### TON

* Uses EQ.../UQ... address format
* Addresses are automatically normalized
* No PnL endpoints

#### Hyperliquid

* Perpetuals platform only
* Used for perp-specific endpoints
* No standard token endpoints


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nansen.ai/reference/chains.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.