{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "bitcoin-transaction-id-vs-address",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/bitcoin-transaction-id-vs-address/",
  "collection": "bitcoin",
  "title": "Bitcoin transaction ID versus wallet address",
  "description": "Distinguish a Bitcoin transaction ID from a receiving address, an output index and a SegWit witness transaction ID.",
  "aliases": [
    "bitcoin transaction id vs address",
    "bitcoin transaction id vs address explained"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T19:29:20.637Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "A Bitcoin address describes a destination for an output under a supported encoding. A transaction ID identifies a serialized transaction, and an output index selects one output within it. They answer different questions: where to pay, which transaction to inspect and which output is being spent. A transaction ID does not prove confirmation or provide the authority to spend its outputs.",
    "claimId": "bitcoin-transaction-id-vs-address-quick-answer",
    "sourceIds": [
      "x425-btc-dev-transactions",
      "x425-btc-bip141",
      "x425-btc-core-sendrawtransaction"
    ]
  },
  "keyFacts": [
    {
      "label": "Address",
      "value": "An encoded payment destination",
      "sourceIds": [
        "x425-btc-dev-transactions"
      ],
      "id": "address",
      "claimId": "bitcoin-transaction-id-vs-address-fact-address"
    },
    {
      "label": "Transaction ID",
      "value": "Identifies transaction data",
      "sourceIds": [
        "x425-btc-bip141"
      ],
      "id": "transaction-id",
      "claimId": "bitcoin-transaction-id-vs-address-fact-transaction-id"
    },
    {
      "label": "Outpoint",
      "value": "Transaction ID plus output index",
      "sourceIds": [
        "x425-btc-dev-transactions"
      ],
      "id": "outpoint",
      "claimId": "bitcoin-transaction-id-vs-address-fact-outpoint"
    }
  ],
  "prerequisites": [
    "how-to-read-a-block-explorer",
    "what-is-a-utxo"
  ],
  "sections": [
    {
      "id": "objects",
      "heading": "One transaction can involve many destinations",
      "sourceIds": [
        "x425-btc-dev-transactions"
      ],
      "paragraphs": [
        "A transaction can spend multiple earlier outputs and create multiple new ones. The new outputs may include recipient payments and change. There is no single mandatory sender address field representing a person.",
        "An address may appear in more than one transaction, so searching an address and searching a transaction ID can produce different views of activity. Neither public identifier is a private signing key."
      ]
    },
    {
      "id": "example",
      "heading": "Use the output index to identify a particular coin",
      "sourceIds": [
        "x425-btc-dev-transactions"
      ],
      "paragraphs": [
        "Suppose a transaction has three outputs indexed 0, 1 and 2. A later input referring to that transaction’s ID and index 1 spends the second output, not all three. The pair is called an outpoint.",
        "A block explorer can show the payment to the recipient separately from change. Do not interpret every output as an extra payment or the total output value as the merchant’s receipt."
      ]
    },
    {
      "id": "witness",
      "heading": "SegWit introduces a second identifier with a different scope",
      "sourceIds": [
        "x425-btc-bip141",
        "x425-btc-core-sendrawtransaction"
      ],
      "paragraphs": [
        "BIP-141 defines the traditional txid from transaction serialization without witness data and a wtxid that includes the witness serialization. Wallets and explorers should indicate which identifier they are using when that distinction matters.",
        "A returned txid from a broadcast call identifies the submitted transaction; it is not a block-inclusion receipt. Check the transaction status and accepted-chain context separately."
      ]
    }
  ],
  "faq": [
    {
      "question": "Can someone spend my bitcoin because they know its transaction ID?",
      "answer": "Knowing the public transaction ID does not supply the signatures or other conditions needed to spend an output. Spending authority comes from satisfying the output’s rules.",
      "sourceIds": [
        "x425-btc-dev-transactions"
      ]
    },
    {
      "question": "Does each Bitcoin address have exactly one transaction ID?",
      "answer": "No. An address can receive outputs in multiple transactions. A transaction can also create outputs for multiple addresses. The two identifiers describe different objects.",
      "sourceIds": [
        "x425-btc-dev-transactions"
      ]
    }
  ],
  "claims": [
    {
      "id": "bitcoin-transaction-id-vs-address-quick-answer",
      "articleSlug": "bitcoin-transaction-id-vs-address",
      "statement": "A Bitcoin address describes a destination for an output under a supported encoding. A transaction ID identifies a serialized transaction, and an output index selects one output within it. They answer different questions: where to pay, which transaction to inspect and which output is being spent. A transaction ID does not prove confirmation or provide the authority to spend its outputs.",
      "sourceIds": [
        "source-b282fdecc069b74d",
        "source-896e868816ad19d1",
        "source-4d4d250c55f548e4"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-b282fdecc069b74d",
          "locator": "Introduction; Spending An Output; P2PKH Script Validation; Multisig; Transaction Fees And Change; Avoiding Key Reuse"
        },
        {
          "sourceId": "source-896e868816ad19d1",
          "locator": "Transaction ID; Additional definitions; Transaction size calculations"
        },
        {
          "sourceId": "source-4d4d250c55f548e4",
          "locator": "Description; Arguments; Result"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02.",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Checked transaction output indices and BIP141 traditionaltxid versus witness-inclusivewtxid serialization. Index1 selects the second output; an identifier is neither spending authority nor a confirmation receipt."
        ]
      }
    },
    {
      "id": "bitcoin-transaction-id-vs-address-fact-address",
      "articleSlug": "bitcoin-transaction-id-vs-address",
      "statement": "Address: An encoded payment destination",
      "sourceIds": [
        "source-b282fdecc069b74d"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-b282fdecc069b74d",
          "locator": "Introduction; Spending An Output; P2PKH Script Validation; Multisig; Transaction Fees And Change; Avoiding Key Reuse"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Checked transaction output indices and BIP141 traditionaltxid versus witness-inclusivewtxid serialization. Index1 selects the second output; an identifier is neither spending authority nor a confirmation receipt."
        ]
      }
    },
    {
      "id": "bitcoin-transaction-id-vs-address-fact-transaction-id",
      "articleSlug": "bitcoin-transaction-id-vs-address",
      "statement": "Transaction ID: Identifies transaction data",
      "sourceIds": [
        "source-896e868816ad19d1"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-896e868816ad19d1",
          "locator": "Transaction ID; Additional definitions; Transaction size calculations"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Checked transaction output indices and BIP141 traditionaltxid versus witness-inclusivewtxid serialization. Index1 selects the second output; an identifier is neither spending authority nor a confirmation receipt."
        ]
      }
    },
    {
      "id": "bitcoin-transaction-id-vs-address-fact-outpoint",
      "articleSlug": "bitcoin-transaction-id-vs-address",
      "statement": "Outpoint: Transaction ID plus output index",
      "sourceIds": [
        "source-b282fdecc069b74d"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-b282fdecc069b74d",
          "locator": "Introduction; Spending An Output; P2PKH Script Validation; Multisig; Transaction Fees And Change; Avoiding Key Reuse"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Checked transaction output indices and BIP141 traditionaltxid versus witness-inclusivewtxid serialization. Index1 selects the second output; an identifier is neither spending authority nor a confirmation receipt."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "x425-btc-dev-transactions",
      "label": "Transactions",
      "publisher": "Bitcoin developer documentation",
      "url": "https://developer.bitcoin.org/devguide/transactions.html",
      "locator": "Introduction; Spending An Output; P2PKH Script Validation; Multisig; Transaction Fees And Change; Avoiding Key Reuse",
      "note": "Inputs, outputs, authorization, change, coinbase exceptions and fee accounting.",
      "version": "Developer guide; historical implementation details require qualification",
      "checkedAt": "2026-10-02T18:53:53.759Z",
      "contentSha256": "2f3fc474d51880e6c7fd4c25f747f8d8d8da49a493ab82af8ff4916fa490d6b8",
      "recordId": "source-b282fdecc069b74d"
    },
    {
      "id": "x425-btc-bip141",
      "label": "Segregated Witness",
      "publisher": "Bitcoin Improvement Proposals",
      "url": "https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0141.mediawiki",
      "locator": "Transaction ID; Additional definitions; Transaction size calculations",
      "note": "Transaction identifiers, weight and virtual size definitions.",
      "version": "Pinned BIPs revision",
      "checkedAt": "2026-10-02T18:53:54.098Z",
      "contentSha256": "d72409335872a32494f75e7547589abf4b3b23b6beebe6bc6999c7a84b135e2c",
      "recordId": "source-896e868816ad19d1"
    },
    {
      "id": "x425-btc-core-sendrawtransaction",
      "label": "sendrawtransaction RPC",
      "publisher": "Bitcoin Core",
      "url": "https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/sendrawtransaction/",
      "locator": "Description; Arguments; Result",
      "note": "Submitting serialized signed transactions, fee guardrails and rebroadcast privacy warning.",
      "version": "Bitcoin Core 29.0 RPC reference; not a recommendation to install an old release",
      "checkedAt": "2026-10-02T18:53:56.420Z",
      "contentSha256": "c1402d0c9c6677bd967fdd20dbb650991a8169c30e1a6598fbed3ac4defbd08a",
      "recordId": "source-4d4d250c55f548e4"
    }
  ],
  "related": {
    "articles": [
      "how-to-read-a-block-explorer",
      "what-is-a-utxo",
      "segwit-explained",
      "bitcoin-block-time-variance",
      "bitcoin-payjoin"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and separate automated verification."
    }
  ],
  "citation": "Degrees of Satoshi editorial project. “Bitcoin transaction ID versus wallet address.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-transaction-id-vs-address/"
}