---
title: "Get UTXO info by tx hash and index"
method: GET
path: "/v4/data/blockchains/utxo/info"
tags: ["Blockchains API"]
---

# Get UTXO info by tx hash and index

`GET /v4/data/blockchains/utxo/info`

/v4/data/blockchains/utxo/info

**10 credits per API call**

Get information about a transaction output (UTXO) by transaction hash and output index. Supported for Bitcoin, Litecoin, Dogecoin, and Bitcoin Cash. Response is normalized: `value` in smallest unit (satoshis), `address`, `script`, `hash`, `index`, and `height` (block height; for mempool/unconfirmed UTXOs, `height` is `-1`). If the output is spent, the API returns 403.

## Query parameters

- `chain` 'bitcoin-mainnet' | 'bitcoin-testnet' | 'litecoin-mainnet' | 'litecoin-testnet' | 'doge-mainnet' | 'dogecoin-testnet' | 'bch-mainnet' | 'bch-testnet', required — UTXO chains supported for GET blockchains/utxo/info.
- `hash` string, required
- `index` integer, required

## Response `200`

OK

- UtxoInfoResponse
  - `value` integer, required — Value in smallest unit (satoshis for BTC/LTC/DOGE/BCH).
  - `address` string, required — Output address.
  - `script` string, required — Script hex.
  - `hash` string, required — Transaction hash.
  - `index` integer, required — Output index (vout) in the transaction.
  - `height` integer, required — Block height. For mempool (unconfirmed) UTXOs, height is -1.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized. Not valid or inactive subscription key present in the HTTP Header.
- `403` — Forbidden. The request is authenticated, but it is not possible to perform the operation due to logical error or invalid permissions.
- `500` — Internal server error. There was an error on the server during the processing of the request.

---

[API](https://skmtc.net/tatum/apis/blockchain-data.md) · [All operations](https://skmtc.net/tatum/apis/blockchain-data/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tatum/blockchain-data/revisions/8622ee4b8fae/schema)