> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dune.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Labels Data

> Labels provide valuable context and clarity to blockchain addresses, enhancing the readability and understanding of blockchain transaction data.

export const DuneEmbed = ({qID, vID, height = '500px'}) => <>
    <div className="hidden dark:block">
      <iframe src={`https://dune.com/embeds/${qID}/${vID}?darkMode=true`} style={{
  width: '100%',
  height,
  border: 'none',
  marginTop: '10px'
}}></iframe>
    </div>
    <div className="dark:hidden">
      <iframe src={`https://dune.com/embeds/${qID}/${vID}`} style={{
  width: '100%',
  height,
  border: 'none',
  marginTop: '10px'
}}></iframe>
    </div>
  </>;

## Why Labels Matter

Labels are more than just simple tags or annotations. They provide valuable context and clarity to blockchain addresses, enhancing the readability and understanding of blockchain transaction data.

<Info>
  **Maintained by:** Dune · **Refresh:** N/A · **Chains:** Cross-chain
</Info>

<Card title="Get This Data" icon="database" href="https://dune.com/enterprise?dataset=labels">
  Access label data via API, Datashare, or the Dune App.
</Card>

In the world of blockchain analysis, labels play a crucial role in identifying and categorizing different entities and activities. They act as signposts, guiding analysts through the complex web of transactions and addresses, making it easier to identify the parties involved and their roles.

By mapping blockchain addresses to **known entities**, labels bring transparency to transaction analysis. They help distinguish between individuals, organizations, smart contracts, and other important actors in the blockchain ecosystem. This clarity is essential for compliance, risk assessment, and investigative purposes.

Labels also provide insights into the roles and functions of addresses, helping analysts understand the nature of transactions and the relationships between different entities in the blockchain ecosystem.

<div>
  <DuneEmbed height="500px" qID={3730609} vID={6274344} />
</div>

## Labels datasets

We provide several label datasets that can be used to enrich your analysis:

<CardGroup cols={2}>
  <Card title="All Labels" icon="maximize" href="/data-catalog/curated/labels/address-labels">
    A comprehensive collection of labeled addresses across various categories and blockchains, serving as a central repository for all labeled entities on Dune.
  </Card>

  <Card title="ENS Labels" icon="signature" href="/data-catalog/curated/labels/ens-labels">
    Ethereum Name Service (ENS) data linking human-readable names with blockchain addresses, facilitating easier interactions and identifications within the Ethereum ecosystem.
  </Card>

  <Card title="Owner Addresses" icon="house" href="/data-catalog/curated/labels/owner-addresses">
    Detailed mapping of blockchain addresses to their owners and custodians, providing insights into ownership and custody of assets across blockchains.
  </Card>

  <Card title="Owner Details" icon="info" href="/data-catalog/curated/labels/owner-details">
    Comprehensive information about entities within the ecosystem, including their operational profiles, categories, and online presence.
  </Card>
</CardGroup>

## When to Use These Tables

* Identify counterparties in transaction analysis (exchanges, protocols, DAOs)
* Enrich compliance workflows with entity attribution
* Build address reputation and risk scoring systems
* Resolve ENS names to blockchain addresses and vice versa
* Track protocol treasury and operational addresses

## Query Performance

`labels.addresses` is a large table. Always filter on `blockchain` and use additional filters where possible.

```sql theme={null}
-- ✅ Good: chain + category filter
SELECT * FROM labels.addresses
WHERE blockchain = 'ethereum'
  AND label_type = 'cex'

-- ❌ Slow: searching by label name across all chains
SELECT * FROM labels.addresses
WHERE name LIKE '%Binance%'
```

## Methodology

Labels are maintained by Dune ([source code](https://github.com/duneanalytics/spellbook)). They aggregate address identifications from multiple sources: manually curated seed files (exchanges, protocols, DAOs), automated contract analysis (factory-deployed contracts, proxy patterns), ENS domain resolution, and community contributions. Labels include entity names, categories (e.g., `cex`, `dex`, `dao`, `bridge`), and metadata about the source of identification.

## Example Queries

**Find all labeled Binance addresses on Ethereum:**

```sql theme={null}
SELECT
  address,
  name,
  label_type,
  model_name
FROM labels.addresses
WHERE blockchain = 'ethereum'
  AND name LIKE '%Binance%'
```

**Resolve ENS name to address:**

```sql theme={null}
SELECT
  address,
  name
FROM labels.ens
WHERE name = 'vitalik.eth'
```

## Related Tables

* `cex.addresses` — CEX-specific address identification (more targeted than labels)
* `tokens.transfers` — Transfer events enriched by label data
* `cex.flows` — Exchange flows that rely on label-identified addresses

<CardGroup cols={2}>
  <Card title="Enterprise Data Solutions" icon="building" href="https://dune.com/enterprise">
    Need custom address labeling or dedicated support? Talk to our enterprise team.
  </Card>

  <Card title="Build Custom Models" icon="code" href="/api-reference/connectors/overview">
    Build private address intelligence pipelines with the dbt Connector.
  </Card>
</CardGroup>