The wallclock duration between a transaction being submitted and achieving a desired commitment level. On Solana, processed confirmation takes ~400ms (leader executes), confirmed (optimistic) takes ~400ms-1s (supermajority votes), and finalized (rooted) typically takes 26-32 slots (~10-13 seconds). Actual confirmation time varies with network congestion, leader distance, and transaction priority fee.
Comece pela explicação mais curta e útil antes de aprofundar.
The wallclock duration between a transaction being submitted and achieving a desired commitment level. On Solana, processed confirmation takes ~400ms (leader executes), confirmed (optimistic) takes ~400ms-1s (supermajority votes), and finalized (rooted) typically takes 26-32 slots (~10-13 seconds). Actual confirmation time varies with network congestion, leader distance, and transaction priority fee.
Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.
Pense nisso como um bloco de construção que ajuda a ligar uma definição isolada ao sistema maior onde ela vive.
Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.
Clusters, nós, atores de MEV, roteamento e ambientes operacionais.
Transforme o termo de vocabulário em algo operacional para produto e engenharia.
Este termo destrava conceitos adjacentes rapidamente, então funciona melhor quando você o trata como um ponto de conexão, não como definição isolada.
Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.
Confirmation Time (confirmation-time) Categoria: Rede Definição: The wallclock duration between a transaction being submitted and achieving a desired commitment level. On Solana, processed confirmation takes ~400ms (leader executes), confirmed (optimistic) takes ~400ms-1s (supermajority votes), and finalized (rooted) typically takes 26-32 slots (~10-13 seconds). Actual confirmation time varies with network congestion, leader distance, and transaction priority fee. Relacionados: Níveis de Compromisso, Finalidade, Transaction Landing
Use contexto do glossário, relações entre termos, modelos mentais e builder paths para receber respostas estruturadas em vez de output genérico.
Opcional: cole código Anchor, Solana ou Rust para o Copilot mapear primitivas de volta para termos do glossário.
O Copilot vai responder usando o termo atual, conceitos relacionados, modelos mentais e o grafo ao redor do glossário.
Esses ramos mostram quais conceitos esse termo toca diretamente e o que existe uma camada além deles.
The three transaction confirmation tiers exposed by Solana RPC: 'processed' (transaction executed by leader, not yet voted on), 'confirmed' (optimistic confirmation—66.7%+ stake voted, ~400ms), and 'finalized' (rooted—31+ confirmations, ~12-13s). Applications choose the level based on their security vs. latency requirements.
The guarantee that a transaction cannot be reversed. Solana offers two levels: optimistic confirmation (~400ms, 66.7%+ stake voted) and full finality (~12-13 seconds, 31+ confirmations rooted). Once a slot is rooted, its transactions are irreversible under the assumption that no more than 1/3 of stake is malicious.
The outcome of a transaction being successfully included and confirmed in a Solana block, as opposed to being dropped, expiring, or failing simulation. Landing probability is influenced by priority fee competitiveness, blockhash freshness (must be within ~150 slots of creation), submission routing (direct to leader vs. RPC rebroadcast), and network congestion on the accounts involved. Developers optimize landing rates by using current-leader TPU endpoints, setting appropriate priority fees, and preflight-checking transactions before submission.
Estes são os próximos conceitos que valem abrir se você quiser que este termo faça mais sentido dentro de um workflow real de Solana.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
The three transaction confirmation tiers exposed by Solana RPC: 'processed' (transaction executed by leader, not yet voted on), 'confirmed' (optimistic confirmation—66.7%+ stake voted, ~400ms), and 'finalized' (rooted—31+ confirmations, ~12-13s). Applications choose the level based on their security vs. latency requirements.
The guarantee that a transaction cannot be reversed. Solana offers two levels: optimistic confirmation (~400ms, 66.7%+ stake voted) and full finality (~12-13 seconds, 31+ confirmations rooted). Once a slot is rooted, its transactions are irreversible under the assumption that no more than 1/3 of stake is malicious.
The outcome of a transaction being successfully included and confirmed in a Solana block, as opposed to being dropped, expiring, or failing simulation. Landing probability is influenced by priority fee competitiveness, blockhash freshness (must be within ~150 slots of creation), submission routing (direct to leader vs. RPC rebroadcast), and network congestion on the accounts involved. Developers optimize landing rates by using current-leader TPU endpoints, setting appropriate priority fees, and preflight-checking transactions before submission.
Essas entradas vivem ao lado do termo atual e ajudam a página a parecer parte de um grafo maior, não um beco sem saída.
Solana's primary production cluster where real SOL and real economic activity occur; the "beta" designation reflects the network's ongoing protocol development despite being fully live since March 2020. It uses the same architecture as other clusters but with real validator stakes, live staking rewards, and permanent on-chain state. All production dApps, tokens, and NFTs exist on Mainnet Beta.
A persistent public Solana cluster intended for application development and testing, running the same software version as Mainnet Beta but with no real economic value. Devnet SOL can be freely airdropped via the CLI or faucet APIs, and the ledger may be reset periodically by Solana Labs. Developers use Devnet to test programs and integrations before deploying to Mainnet Beta.
A public Solana cluster used primarily by the Solana core team and validators to test new software releases, performance benchmarks, and network upgrades under real network conditions before they reach Mainnet Beta. Testnet SOL has no monetary value, and the ledger is reset more frequently than Devnet; it is less suitable for application development and more suited for validator operators validating their infrastructure.
The rate at which a Solana cluster processes and commits transactions; Solana's theoretical maximum exceeds 65,000 TPS due to its parallel execution model, though real-world sustained throughput on Mainnet Beta typically ranges from 2,000–5,000 non-vote TPS under normal load. Vote transactions (used for consensus) make up a significant portion of all on-chain activity and are counted separately. High TPS is enabled by Proof of History timestamps, Sealevel parallel execution, and Gulf Stream mempool-less forwarding.