From a Bitcoin block to its transactions
Find a block, inspect its transactions and understand their sizes, fees and outputs. Each page remains a specific captured result.
1. Choose a block by height or hash
The view starts with the provider’s ten latest blocks. Select a block or enter its height or full hash, then apply the draft. Height is a position in the chain; a hash identifies a particular block. A reorganization can map the same height to another hash.
Block facts, chain status and a transaction page have their own sources and clocks. Block time comes from its header, while response capture records when Datisto received the data. The latest displayed block is not an independently verified tip of the entire network.
2. Keep pagination inside the same block
One source page contains up to 25 transactions. The next page keeps the selected hash; a new block must not automatically replace your choice during browsing. The block’s total transaction count and the currently loaded row count are different quantities.
Changing a block or source page creates a new applied result. Selecting a transaction, local search and sorting only change how that batch is viewed. This does not crawl blockchain history or automatically download every transaction.
3. The map represents virtual size
A transaction’s map area follows its virtual size in vB: weight divided by four and rounded up. It does not represent the value of bitcoin transferred. Weight in WU, serialized size in bytes and virtual size are distinct measures.
A fee is an amount of satoshis; a fee rate is satoshis per vB. Its exact numerator and denominator remain in details and exports, while the displayed decimal is shortened. Fees summed over the loaded page are not the fees of every transaction in the block.
4. Inputs, outputs and coinbase have different roles
Details show each original previous-output reference, its known value and the new outputs. Total output value is not automatically economic trade volume: it may include change and several recipients. An address or script type does not establish an actual owner.
Coinbase is the block’s special transaction. Its absent previous output is not an error, and its outputs are neither an ordinary transfer between two users nor a miner’s net profit. Unknown previous-output values remain unknown. The normalized detail omits complete signatures, witness data and full scripts; it is not a cryptographic transaction verifier.
5. Source status and exports belong to the captured result
Best-chain status is a provider observation with its own capture. A block outside that chain or an unknown status stays explicitly labelled. A negative status does not become confirmation merely because another older response still labels a transaction confirmed. This view verifies neither a Merkle proof nor every consensus rule.
Complete JSON and CSV contain the applied query, source contexts, normalized block facts, the entire loaded transaction page, its inputs and outputs, and the common manifest. They do not export every transaction in the block.
This is a guide to Datisto. Private features require sign-in and access to your own data. Personal models use your assumptions; availability and permitted use of source data are checked with the particular result. This is not investment advice.