Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
LABS
Glossary

Arweave Transaction ID

An Arweave Transaction ID (TXID) is a unique cryptographic hash that serves as a permanent, immutable identifier for a piece of data stored on the Arweave permaweb.
Chainscore © 2026
definition
BLOCKCHAIN IDENTIFIER

What is an Arweave Transaction ID?

A unique cryptographic identifier for any data or payment permanently recorded on the Arweave network.

An Arweave Transaction ID (TXID) is a unique, 43-character, base64url-encoded cryptographic hash that serves as the immutable identifier for any action recorded on the Arweave blockchain. It is generated by hashing the transaction's data and metadata, creating a digital fingerprint that is globally unique. This ID is the primary reference point for retrieving data, verifying its integrity, and tracking its on-chain history, functioning similarly to a permanent, unforgeable receipt for data storage or value transfer.

Every transaction on Arweave, whether it's uploading a file (a data transaction), sending $AR tokens (a wallet-to-wallet transaction), or interacting with a SmartWeave contract, is assigned its own TXID. This ID is crucial for the network's Proof of Access consensus mechanism, as it is used to cryptographically link data blocks together. You can look up any transaction's details, including its data, tags, and block height, by using a block explorer like ViewBlock or Arweave's own Arweave.net gateway.

The structure of a typical Arweave TXID, such as ujpzWgP0dM5QOHmSDjD_qF5Q2FJlTZ4Rr7W_1JZ1b3E, is designed for compactness and compatibility with URLs. Developers use this ID as a direct pointer to stored data; appending a TXID to an Arweave gateway URL (e.g., https://arweave.net/<TXID>) fetches the associated content. This makes Arweave TXIDs the foundational unit for building permanent, decentralized applications (dApps) and archives, as they provide a verifiable and permanent address for any piece of stored information.

how-it-works
BLOCKCHAIN IDENTIFIER

How an Arweave Transaction ID Works

An Arweave Transaction ID is a unique cryptographic hash that serves as a permanent, immutable identifier for data stored on the Arweave permaweb.

An Arweave Transaction ID (TXID) is a 43-character, Base64URL-encoded string derived from the SHA-256 hash of the transaction's bundled data and metadata. It functions as a globally unique, content-addressed pointer to a specific piece of data—such as a file, smart contract, or interaction—permanently stored on the Arweave network. This ID is the fundamental key used to retrieve and verify the integrity of the stored data, ensuring that any tampering would produce a completely different hash and thus a different TXID.

The generation of a TXID is a core part of Arweave's Proof of Access consensus mechanism. When a user submits data, the network bundles it into a transaction containing the data payload, tags for metadata, and a cryptographic signature. This entire bundle is hashed to create the TXID, which is then permanently recorded on the Arweave blockweave. The ID is intrinsically linked to the data's content; even a single bit change results in a new, distinct identifier, providing a robust mechanism for data integrity verification.

From a developer's perspective, the TXID is the primary handle for interacting with stored data. Applications reference assets like images, web pages, or smart contract states using their immutable TXIDs via gateways (e.g., arweave.net/TXID). This system enables permanent data permanence, as the ID guarantees the data retrieved is the exact data originally stored. Common transaction types each have a TXID, including data uploads, wallet-to-wallet transfers of the $AR token, and interactions with SmartWeave smart contracts.

key-features
BLOCKCHAIN IDENTIFIER

Key Features of an Arweave TXID

An Arweave Transaction ID (TXID) is the unique, permanent cryptographic identifier for any piece of data or action recorded on the Arweave permaweb. This card grid breaks down its defining characteristics.

01

Immutable & Permanent Identifier

An Arweave TXID is a cryptographic hash (SHA-256) of the transaction's data and metadata, creating a content-addressable pointer. Once mined into a block, the data it references is guaranteed to be stored for a minimum of 200 years, making the TXID a permanent, unchangeable proof of existence.

02

Structure & Composition

A TXID is a 43-character, base64url-encoded string (e.g., -8A6RexFkpfWwuyVO98wzSFZh0d6VJuI-bhTJvGfLIA). It is derived from the transaction's data root, tags, and other headers. This structure ensures that even a single bit change in the original data results in a completely different, verifiable TXID.

04

Types of Transactions

TXIDs identify different on-chain actions:

  • Data Transactions: For storing files (images, web apps, PDFs).
  • Wallet Transactions: For transferring $AR tokens between addresses.
  • Smart Contract Interactions: For deploying or interacting with SmartWeave contracts. Each type shares the same immutable TXID structure but contains different internal data formats.
05

Verification & Trustlessness

Any user can independently verify that data retrieved via a TXID is authentic by:

  1. Recomputing the data root and comparing it to the one in the transaction.
  2. Validating the cryptographic Merkle proof that links the data to a confirmed block on the blockweave. This process requires no trusted third parties.
primary-use-cases
ARWEAVE TRANSACTION ID

Primary Use Cases

An Arweave Transaction ID (TXID) is a unique, permanent identifier for data stored on the Arweave network. It is a cryptographic hash that serves as the primary reference for retrieving and verifying data.

02

Content Verification & Provenance

Each TXID is a cryptographic fingerprint (SHA-256 hash) of the transaction's data and metadata. This allows anyone to:

  • Verify data integrity by hashing the retrieved data and comparing it to the TXID.
  • Establish immutable provenance by tracing the transaction back through the blockweave.
  • Prove a specific piece of data existed at a certain time, as the TXID is permanently recorded in a block. This is fundamental for notarization, audit trails, and digital art authenticity (e.g., NFTs).
nft-metadata-application
PERMANENT STORAGE

Application in NFT Metadata

An Arweave Transaction ID (TXID) is a unique cryptographic hash that serves as a permanent, immutable pointer to data stored on the Arweave network. In the context of NFTs, this ID is the foundational link that ensures the artwork, attributes, and other metadata remain accessible and verifiable forever, decoupling the NFT's value from the potential failure of centralized servers.

An Arweave Transaction ID (TXID) is the critical component that enables permanent data storage for NFTs. Unlike traditional cloud storage or even standard decentralized solutions like IPFS, which rely on ongoing pinning and network participation, data written to Arweave is guaranteed to persist for a minimum of 200 years through a novel endowment mechanism. When an NFT's image and metadata are uploaded to Arweave, the platform returns a unique, immutable TXID—a string like ak7...q9z. This hash is then embedded directly into the NFT's smart contract on its native blockchain (e.g., Ethereum, Solana), creating an unbreakable cryptographic link to the asset.

The technical implementation involves storing the Arweave TXID within the NFT's tokenURI or metadata URI field. A common pattern is to use an Arweave gateway URL, such as https://arweave.net/<TXID>, which resolves to a JSON metadata file. This file itself contains the TXID for the image and other assets. This chaining of permanent references ensures that even if the original minting platform disappears, the data remains independently retrievable and verifiable by anyone using the public TXID. This solves the critical problem of link rot and content mutability that plagues many early NFTs.

For developers and collectors, verifying an NFT's permanence involves checking the metadata for an Arweave TXID. Key tools include blockchain explorers to view the on-chain tokenURI and Arweave's own block explorer, ViewBlock. A best practice is for the metadata JSON to reference assets using the Arweave-permaweb URI scheme (ar://<TXID>), which is protocol-agnostic and directs clients to the appropriate gateway. This approach future-proofs the asset against gateway deprecation, as the canonical reference remains the immutable TXID itself.

Prominent NFT projects like Solana's Metaplex standard have integrated Arweave storage by default, baking permanent metadata into their minting process. The economic model is also distinct: a single, upfront fee paid in AR tokens covers the cost of storing the data for centuries, unlike recurring subscription models. This makes the Arweave TXID not just a technical pointer but also a financial guarantee of persistence, aligning long-term asset integrity with a sustainable economic incentive for the network's miners, known as miners.

DATA ANCHORS

Comparison with Other Blockchain Identifiers

How Arweave's Transaction ID differs from identifiers on other major blockchain platforms in terms of structure, function, and permanence.

Feature / MetricArweave Transaction IDEthereum Transaction HashBitcoin Transaction ID (TXID)

Primary Function

Anchors data permanently to the Arweave network

Records a state change on the Ethereum Virtual Machine (EVM)

Records a transfer of value (BTC) on the Bitcoin ledger

Data Referenced

Direct cryptographic hash of the stored data payload

Hash of transaction data (to, from, value, input data)

Hash of transaction data (inputs, outputs, scripts)

Data Permanence

Permanent, on-chain storage via proof-of-access consensus

Ephemeral; data persists only if stored in contract state or logs

Ephemeral; only UTXO state is permanent, not arbitrary data

Content Addressing

True. ID is a hash of the content, enabling deterministic retrieval

Indirect. Input data is hashed, but not used as a primary retrieval key

No. ID is a hash of the transaction, not its data payload

Human-Readable (Base64URL)

Yes. Uses URL-safe Base64 encoding (e.g., abc123...)

No. Uses Base16 (hexadecimal) encoding (e.g., 0xabc123...)

No. Uses Base16 (hexadecimal) encoding (e.g., abc123...)

Typical Length (chars)

43 characters

66 characters (0x + 64 hex chars)

64 characters

Underlying Hash Function

SHA-256

Keccak-256

SHA-256 (double-hashed)

Serves as Payment for Storage

Yes. Transaction fee pays for permanent storage endowment

No. Fee pays for execution/validation, not data persistence

No. Fee pays for miner priority, not data persistence

technical-properties
ARWEAVE TRANSACTION ID

Technical Properties & Structure

An Arweave Transaction ID is a unique, permanent cryptographic identifier for any piece of data or interaction on the Arweave network. It is the foundational reference for retrieving and verifying stored content.

01

Cryptographic Hash

The Transaction ID is a Base64URL-encoded SHA-256 hash of the transaction's data field and its associated tags. This creates a deterministic, unique fingerprint. Any alteration to the data or tags would produce a completely different ID, ensuring immutability and data integrity. The hash function is applied to the raw binary data before any encoding.

02

Format & Encoding

The hash is encoded in Base64URL (RFC 4648), a URL-safe variant of Base64 that replaces + and / with - and _. This results in a compact, 43-character string (e.g., T1qE6v5J8QZzQ7Q9Q1Q2Q3Q4Q5Q6Q7Q8Q9Q0Q1Q2Q3Q4Q5Q6Q7Q8Q9Q0). The encoding ensures the ID can be safely transmitted in URLs, JSON, and filenames without special escaping.

04

Components of the Hashed Data

The SHA-256 input includes specific, ordered transaction fields:

  • Data Root: The Merkle root of the data chunks.
  • Last TX: The ID of the previous transaction from the same wallet (for proof-of-access).
  • Owner: The public key of the transaction signer.
  • Tags: An array of name-value pairs (also Base64URL encoded).
  • Target & Quantity: For financial transfers. This structured hashing binds all transaction metadata immutably to the ID.
05

Distinction from Data Root

A Transaction ID is often confused with a Data Root, but they are distinct hashes. The Data Root is a Merkle root hash of the data's 256KB chunks. The Transaction ID is a hash of the transaction structure including this Data Root and other metadata. You need the Transaction ID to fetch the transaction and its Data Root from the network, which is then used to reconstruct the original file.

06

Verification & Proofs

The ID enables cryptographic verification. Using the blockweave history and Proof of Access consensus, any node can prove that the data corresponding to a given Transaction ID is stored and accessible on the network. Clients can verify data integrity by recomputing the Data Root from retrieved chunks and checking it against the value in the transaction referenced by the ID.

ARWEAVE TRANSACTION ID

Common Misconceptions

Clarifying frequent misunderstandings about the unique identifiers for data stored on the Arweave permaweb.

No, an Arweave Transaction ID is not the same as a file hash; it is the unique identifier for the transaction that posted the data to the network, not the data itself. The transaction ID is a 43-character, URL-safe Base64URL encoded string derived from the transaction's cryptographic signature. The actual data is referenced within the transaction's data field and has its own separate cryptographic hash. While you can retrieve the data using the transaction ID, the ID itself does not directly represent the content's fingerprint, which is a critical distinction for data integrity verification.

ARWEAVE TRANSACTION ID

Frequently Asked Questions (FAQ)

Common questions about the unique identifier for data uploads and transfers on the Arweave permanent storage network.

An Arweave Transaction ID (TXID) is a unique, 43-character Base64URL-encoded cryptographic hash that serves as the immutable identifier for any piece of data, bundle of data, or token transfer recorded on the Arweave network. It is generated by hashing the transaction's data and metadata, creating a permanent, unforgeable reference. This TXID is the primary key used to retrieve stored data via gateways (e.g., arweave.net/tx/<TXID>) and to verify the transaction's existence and integrity on the blockweave. It functions as both a content address and a proof of the data's permanent storage commitment.

ENQUIRY

Get In Touch
today.

Our experts will offer a free quote and a 30min call to discuss your project.

NDA Protected
24h Response
Directly to Engineering Team
10+
Protocols Shipped
$20M+
TVL Overall
NDA Protected Directly to Engineering Team
Arweave Transaction ID: Definition & Use in NFTs | ChainScore Glossary