unisat-dev-docs

Runes Balance and UTXO

This document describes all endpoints and details related to Runes token balance and UTXO management in UniSat OpenAPI.


1. Runes Model Overview

Runes uses a UTXO-based model: assets are attached directly to UTXOs. The Runes indexer does not support mempool (unconfirmed transaction) recognition. This means:

Warning: Always be cautious when spending UTXOs that may contain Runes assets, especially if they are unconfirmed. The indexer cannot detect Runes in mempool transactions, so asset loss may occur if not handled properly.


2. Runes Balance & UTXO Endpoints


3. Usage Scenarios and Special Cases


4. FAQ

Q: How do I get all my Runes balances? A: Use /v1/indexer/address/{address}/runes/balance-list to get all Runes balances for an address.

Q: How do I get the UTXO distribution for a specific Rune? A: Use /v1/indexer/address/{address}/runes/{runeid}/utxo.

Q: What should I be careful about when spending UTXOs? A: Never spend unconfirmed UTXOs as BTC if they may contain Runes assets. The indexer cannot detect Runes in mempool, and you risk sending your Runes to someone else by mistake.

Q: How do I get pure BTC UTXOs (excluding Runes assets)? A: Use /v1/indexer/address/{address}/available-utxo-data to get UTXOs that do not contain Runes assets. This endpoint is designed to help you safely select UTXOs for BTC transactions without risking accidental transfer of Runes.


5. References


6. Indexer Height and Data Lag