An atomic unit of execution containing one or more instructions, a recent blockhash, and one or more signatures. All instructions in a transaction execute sequentially and atomically—if any instruction fails, the entire transaction reverts. Transactions have a 1,232-byte size limit (matching IPv6 MTU) and a default 200,000 CU budget.
Empieza por la explicación más corta y útil antes de profundizar.
An atomic unit of execution containing one or more instructions, a recent blockhash, and one or more signatures. All instructions in a transaction execute sequentially and atomically—if any instruction fails, the entire transaction reverts. Transactions have a 1,232-byte size limit (matching IPv6 MTU) and a default 200,000 CU budget.
Usa primero la analogía corta para razonar mejor sobre el término cuando aparezca en código, docs o prompts.
Piensa en ella como el sobre de ejecución que lleva una o más instrucciones por el runtime.
Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.
Accounts, instrucciones, PDAs, transacciones y flujo de ejecución.
Convierte el término de vocabulario en algo operacional para producto e ingeniería.
Se vuelve más útil cuando navegas por Ruta de Runtime y necesitas vocabulario aterrizado dentro de un flujo real de build.
Usa este bloque compacto cuando quieras dar contexto sólido a un agente o asistente sin volcar toda la página.
Transacción (transaction) Categoría: Modelo de Programación Definición: An atomic unit of execution containing one or more instructions, a recent blockhash, and one or more signatures. All instructions in a transaction execute sequentially and atomically—if any instruction fails, the entire transaction reverts. Transactions have a 1,232-byte size limit (matching IPv6 MTU) and a default 200,000 CU budget. Aliases: TX Relacionados: Instrucción, Firma, Message
Usa contexto del glosario, relaciones entre términos, modelos mentales y builder paths para recibir respuestas estructuradas en vez de output genérico.
Opcional: pega código Anchor, Solana o Rust para que el Copilot mapee primitivas de vuelta al glosario.
El Copilot responderá usando el término actual, conceptos relacionados, modelos mentales y el grafo alrededor del glosario.
Estas ramas muestran qué conceptos toca este término directamente y qué existe una capa más allá de ellos.
A single operation within a transaction that invokes a program. An instruction specifies: (1) the program ID to call, (2) an array of account metas (pubkey, is_signer, is_writable), and (3) an opaque data byte array. Programs decode the instruction data to determine which operation to perform.
A 64-byte Ed25519 digital signature over a transaction's message. Each signer in a transaction produces one signature. The first signature (from the fee payer) also serves as the unique transaction ID. Signature verification is parallelized in the TPU's sigverify stage using GPU acceleration.
The unsigned payload of a transaction containing: a header (signer/read-only counts), an array of account public keys, a recent blockhash, and compiled instructions. Signers sign the serialized message bytes. In v0 messages, an additional section references address lookup tables.
Estos son los siguientes conceptos que vale la pena abrir si quieres que este término tenga más sentido dentro de un workflow real de Solana.
Estas entradas son fáciles de mezclar cuando lees rápido, haces prompting a un LLM o estás entrando en una nueva capa de Solana.
A transaction format introduced with v0 that supports address lookup tables. Legacy transactions include all pubkeys inline (limited to ~35 accounts); v0 transactions reference ALTs to include up to 256 accounts while staying within the 1,232-byte limit. The version byte (0) precedes the message.
The hard upper limit of 1,400,000 compute units that a single Solana transaction can consume. This cap applies regardless of the SetComputeUnitLimit instruction value — no transaction can request more than 1.4M CU. The default per-instruction budget is 200,000 CU, but multi-instruction transactions share the overall 1.4M cap. Transactions exceeding their CU limit fail with a ComputeBudgetExceeded error.
The simulateTransaction RPC method that dry-runs a transaction against a specified bank state without submitting it to the network or consuming fees. Simulation returns the execution result including logs, compute units consumed, return data, and any error. Developers use simulation to estimate CU usage, debug program errors, and verify transaction correctness before sending. Simulation does not require valid signatures.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
A single operation within a transaction that invokes a program. An instruction specifies: (1) the program ID to call, (2) an array of account metas (pubkey, is_signer, is_writable), and (3) an opaque data byte array. Programs decode the instruction data to determine which operation to perform.
A 64-byte Ed25519 digital signature over a transaction's message. Each signer in a transaction produces one signature. The first signature (from the fee payer) also serves as the unique transaction ID. Signature verification is parallelized in the TPU's sigverify stage using GPU acceleration.
The unsigned payload of a transaction containing: a header (signer/read-only counts), an array of account public keys, a recent blockhash, and compiled instructions. Signers sign the serialized message bytes. In v0 messages, an additional section references address lookup tables.
Usa estas rutas cuando quieras pasar de un lookup aislado a una exploración guiada.
Entiende cómo Solana ejecuta trabajo antes de optimizar o debuggear.
Estas entradas viven junto al término actual y ayudan a que la página se sienta parte de un grafo de conocimiento más amplio en lugar de un callejón sin salida.
The fundamental data storage unit on Solana. Every piece of state is stored in an account identified by a 32-byte public key. Accounts hold a lamport balance, an owner program, a data byte array (up to 10MB), and an executable flag. Only the owning program can modify an account's data, but anyone can credit lamports to it.
Executable code deployed on-chain, equivalent to a smart contract on other blockchains. Programs are stateless—they store no data themselves but read/write data in separate accounts they own. Programs are compiled to SBF bytecode and loaded via the BPF Loader. Every program has a unique Program ID (its account's public key).
A single operation within a transaction that invokes a program. An instruction specifies: (1) the program ID to call, (2) an array of account metas (pubkey, is_signer, is_writable), and (3) an opaque data byte array. Programs decode the instruction data to determine which operation to perform.
A transaction format introduced with v0 that supports address lookup tables. Legacy transactions include all pubkeys inline (limited to ~35 accounts); v0 transactions reference ALTs to include up to 256 accounts while staying within the 1,232-byte limit. The version byte (0) precedes the message.