In the rapidly evolving world of Web3 and blockchain technology, accessing accurate, real-time on-chain data is essential for developers, analysts, and crypto enthusiasts alike. One of the most powerful tools in this space is the ability to query inscription transaction details using just a transaction hash. Whether you're tracking BRC-20 tokens, Runes, ARC-20 assets, or Ordinals NFTs, having a reliable API endpoint makes all the difference.
This guide dives deep into how you can retrieve detailed inscription transaction data across multiple Bitcoin-based chains — including BTC and Fractal Bitcoin — using a secure and scalable Wallet API. Designed for developers integrating Web3 services, this documentation ensures seamless access to critical blockchain insights.
👉 Discover powerful on-chain analytics tools that simplify blockchain development
Querying Inscription Transaction Details
The core functionality of this API allows users to fetch comprehensive transaction information by providing a transaction hash (txHash). This feature supports various token standards built on Bitcoin’s ecosystem, enabling granular visibility into token behavior and movement.
Supported Token Standards
The system currently supports the following protocols:
- BRC-20 – Popular fungible tokens on the Bitcoin blockchain
- Runes – A lightweight protocol for creating fungible tokens on Bitcoin
- ARC-20 – Advanced token standard leveraging Atomicals protocol
- SRC-20 – Scalable fungible token model on Bitcoin
- Ordinals NFTs – Unique non-fungible digital collectibles inscribed on Bitcoin
Additionally, BRC-20 transaction queries are also supported on the Fractal Bitcoin chain, expanding cross-chain interoperability for developers building on alternative BTC layers.
API Endpoint Overview
To retrieve inscription transaction details, use the following RESTful GET request:
GET https://web3.okx.com/api/v5/wallet/post-transaction/inscription-transaction-detail-by-txhashThis endpoint is optimized for speed and accuracy, returning structured JSON responses with full transaction metadata.
Request Parameters
Each request must include specific parameters to ensure precise data retrieval. Below are the required and optional fields:
| Parameter | Type | Required | Description |
|---|---|---|---|
chainIndex | String | Yes | Unique identifier for the target blockchain (e.g., BTC, Fractal BTC) |
txHash | String | Yes | The transaction hash to query |
protocol | String | No | Protocol type: 1 (BRC-20), 2 (ARC-20), 3 (Runes), 4 (Ordinals NFT), 5 (SRC-20). Defaults to BRC-20 if not specified |
cursor | String | No | Pagination cursor for retrieving subsequent result sets |
limit | String | No | Number of records to return per call; default is 20, maximum is 100 |
These parameters allow flexible querying, whether you're debugging a single transaction or analyzing large-scale token activity.
Response Structure
Upon successful request, the API returns a structured JSON object containing detailed transaction data.
Key Response Fields
transactionDetails(Array)
An array of transaction objects with the following properties:txStatus: Transaction status —successorfail. Pending transactions are not supported.from: Sender address(es); comma-separated for multisig inputs.to: Receiver address(es); comma-separated for multisig outputs.eventType: Type of transaction based on protocol:- BRC-20:
deploy,mint,inscribeTransfer,transfer - Runes:
Etch,Mintoutput,Burninput,Mint - ARC-20:
atomical-create-ft,ft-color-split,ft-color-regular,distributed-mint - SRC-20:
mint,transfer,deploy - Ordinals NFT:
mint,transfer
- BRC-20:
protocol: Numeric code indicating the token standard used.txHash: Original transaction hash.blockHash: Hash of the block containing the transaction.height: Block height at which the transaction was confirmed.txTime: Timestamp in Unix milliseconds (e.g.,1597026383085).amount: Quantity transferred.symbol: Token ticker symbol (e.g., ORDI, RUNE).tokenInscriptionId: Unique identifier for the inscribed token:- For Runes: Returns the Rune ID
- For BRC-20: Returns Inscription ID
- For ARC-20: Returns Atomical ID
- For others: May be empty
inscriptionNumber: Sequential number assigned to each inscription.outputIndex: UTXO index relevant only for Runes token transfers.
cursor(String)
Pagination cursor for fetching the next batch of results when available.
This level of detail empowers developers to build robust dashboards, audit trails, and analytics engines for Bitcoin-native assets.
Use Cases and Practical Applications
Understanding inscription transactions opens up numerous possibilities:
- Wallet Development: Integrate real-time balance tracking for BRC-20 and Runes tokens.
- Marketplace Analytics: Monitor minting and transfer trends for emerging Ordinals NFTs.
- Fraud Detection: Identify suspicious patterns such as rapid inscribe-transfers or duplicate deployments.
- Blockchain Explorers: Enhance user experience by displaying rich metadata for inscriptions.
👉 Access advanced Web3 APIs to power your next blockchain project
Frequently Asked Questions (FAQ)
What is an inscription transaction?
An inscription transaction refers to the process of embedding data — such as tokens or digital art — directly onto a Bitcoin UTXO using protocols like Ordinals or Runes. These transactions create unique digital assets that can be tracked and transferred across the network.
Can I query pending inscription transactions?
No. The API only returns confirmed transactions with a status of either success or fail. Pending transactions are not supported due to potential malleability and confirmation uncertainty.
How do I distinguish between BRC-20 and Runes tokens in the response?
Use the protocol field:
- Value
1= BRC-20 - Value
3= Runes
Additionally, check theeventTypeandtokenInscriptionIdfields for protocol-specific formats like Inscription ID vs Rune ID.
Is there rate limiting on this API?
While specific rate limits are not disclosed publicly, it's recommended to implement retry logic with exponential backoff and cache frequently accessed transaction hashes to optimize performance.
Does this work with testnet or only mainnet?
Currently, the API supports mainnet chains only. Ensure you're using live network transaction hashes for accurate results.
How often is the data updated?
Transaction data is synced in near real-time with blockchain confirmations. Once a block is finalized on-chain, associated inscription details become immediately available via the API.
Final Thoughts
As Bitcoin continues to evolve beyond simple peer-to-peer payments, tools that unlock deeper on-chain insights become increasingly valuable. With support for BRC-20, Runes, ARC-20, SRC-20, and Ordinals NFTs — across both BTC and Fractal Bitcoin — this Wallet API delivers unmatched flexibility for developers building the next generation of Web3 applications.
Whether you're verifying a mint event, tracing token lineage, or building a full-fledged explorer, having direct access to structured inscription data streamlines development and enhances user trust.
👉 Start exploring blockchain data with powerful Web3 API tools today
By leveraging this service, developers gain a competitive edge in delivering fast, transparent, and reliable blockchain experiences — all without managing node infrastructure or parsing raw blockchain data manually.