Skip to main content
Query Bitcoin transaction inputs filtered by prevout script type to analyze spending patterns across address types.

​
Use Case

Analyze Bitcoin inputs to:
  • Track Taproot adoption by monitoring witness_v1_taproot inputs
  • Analyze UTXO spending patterns by script type
  • Monitor value flow from specific address types
  • Build spending analytics dashboards

​
Sample Response

{
  "header": {
    "number": 880000,
    "timestamp": 1737337343
  },
  "inputs": [
    {
      "transactionIndex": 9,
      "inputIndex": 0,
      "txid": "80e6a90b473e8fd1e70f3e2844dc24b679728d1c23d581a0f6b849d4e9c1fddf",
      "vout": 0,
      "prevoutValue": 0.68954682,
      "prevoutScriptPubKeyType": "witness_v1_taproot",
      "prevoutScriptPubKeyAddress": "bc1p2vnhpsfmyfz4259zdw9jddvq2nnnktev9gz4ggqnqf3pf660z04q8ar0ka"
    }
  ]
}

​
Field Descriptions

  • transactionIndex - Index of the parent transaction within the block
  • inputIndex - Index of this input within the transaction
  • txid - Transaction ID of the output being spent (the prevout reference, not the input’s own transaction)
  • vout - Index of the output being spent in the referenced transaction
  • prevoutValue - Value of the spent output in BTC, returned as a decimal float (not satoshis)
  • prevoutScriptPubKeyType - Script type of the spent output (e.g. witness_v1_taproot)
  • prevoutScriptPubKeyAddress - Address of the spent output
Coinbase inputs. The coinbase input (transactionIndex 0 in each block) mints new value rather than spending a prior output, so prevoutValue and prevoutScriptPubKeyAddress come back as null. Skip or special-case it in flow logic.Joining to the parent transaction. The txid above is the spent output’s transaction. To get the txid of the transaction this input belongs to, request the transactions table ("transactions": [{}]) and join by transactionIndex.