Solana

Jump to bottom

Andrei Montchik edited this page Apr 15, 2026 · 1 revision

Docs

Links

Info

Maximum Transmission Unit a.k.a MTU size in Solana network is 1_280 bytes. That dictates the shred size.
There are around 600-700 shreds in a block.
At most one block is being generated per a slot. It is possible to have slots without blocks, meaning the blocks were missed. The usually cause if Leading Validator to be down, delinquent or building blocks off a fork.
There are 2 slots per second and 432_000 slots total in an epoch, meaning the epoch time is around 60 hours.
There are 64 ticks per block. Ticks are coming from the proof of history a.k.a. PoH thread. Each tick contains 64_000_000 PoH hashes that can be used for ???.
Conversion between Sol, lamports and micro-lamports:
- 1 Sol is 1_000_000_000 lamports.
- 1 lamport is 1_000_000 micro-lamports.
- 1 Sol is 1_000_000_000_000_000 micro-lamports.
- 1 lamport is 0.000_000_001 sol.
- 1 micro-lamport is 0.000_001 lamports.
- 1 micro-lamport is 0.000_000_000_000_001 Sols.
Transaction Info

Install

Components

Cluster

Validator

RPC Node

Wallet

Solana Bigtable

Dev Resources

How To

Solana CLI

Update Solana to the latest version: solana-install update
Update Solana to specific version: solana-install init 1.17.22
Review Solana CLI config: solana config get
Configure Solana CLI to work with specific cluster: solana config set -[um|ut|ud|ul]
Download the confirmed block: solana block <slot>
Work with keypairs: solana-keygen --help.
Cluster CLI
Ledger CLI
Transactions CLI
Wallet CLI
SPL Tokens CLI