---
title: "POST /address/used"
method: POST
path: "/address/used"
---

# POST /address/used

`POST /address/used`

Ordered lexicographically (order is not maintained)

Warning: the pagination on this endpoint is NOT whether or not an address was used during this block interval,
but rather whether or not the address was first used within this interval.

Note: this endpoint only returns addresses that are in a block. Use another tool to see mempool information

## Request body

- AddressUsedRequest
  - `addresses` Address[], required
    - union — Supported types: - Credential hex (8200581c...) - note this is not a keyhash (it contains a credential type prefix) - Bech32 full address (`addr` / `addr_test` / `stake` / `stake_test`) - Bech32 credentials ( `addr_vkh`, `script`, etc.) - this is the recommended approach - Legacy Byron format (Ae2, Dd, etc.) Note: we recommend avoiding to query base addresses history using bech32 As Cardano UTXO spendability depends only on the payment credential and not the full base address The result will also miss transactions that are only related to the payment key of the address ex: the payment key is used in a multisig Note: using two different address representations in the same query will hurt performance (ex: addr1 and addr_vkh1) This because under-the-hood this will run multiple independent SQL queries for the different formats Warning: querying reward bech32 addresses is equivalent to querying the stake credential inside it This may return more results than expected (ex: a multisig containing the staking key of the wallet)
      - string
      - string
      - string
      - string
  - `after` BlockTxPair
    - `tx` string, required — tx hash
    - `block` string, required — block hash
  - `untilBlock` string, required — block hash - inclusive

## Response `200`

- AddressUsedResponse
  - `addresses` Address[], required
    - union — Supported types: - Credential hex (8200581c...) - note this is not a keyhash (it contains a credential type prefix) - Bech32 full address (`addr` / `addr_test` / `stake` / `stake_test`) - Bech32 credentials ( `addr_vkh`, `script`, etc.) - this is the recommended approach - Legacy Byron format (Ae2, Dd, etc.) Note: we recommend avoiding to query base addresses history using bech32 As Cardano UTXO spendability depends only on the payment credential and not the full base address The result will also miss transactions that are only related to the payment key of the address ex: the payment key is used in a multisig Note: using two different address representations in the same query will hurt performance (ex: addr1 and addr_vkh1) This because under-the-hood this will run multiple independent SQL queries for the different formats Warning: querying reward bech32 addresses is equivalent to querying the stake credential inside it This may return more results than expected (ex: a multisig containing the staking key of the wallet)
      - string
      - string
      - string
      - string

## Other responses

- `400`
- `409`
- `422`

---

[API](https://skmtc.dev/dcspark/apis/carp.md) · [All operations](https://skmtc.dev/dcspark/apis/carp/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/dcspark/carp/revisions/ab189523ed9a/schema)