A block is a linked record
A Bitcoin block groups transaction data and links to the preceding block through its header. Explorers make those links navigable so you can connect a confirmed transaction to a particular place in the chain. The Bitcoin blockchain developer guide explains the underlying structure.
Height and hash answer different questions
Block height describes a position in the chain. A block hash identifies a particular block. Competing blocks can share a height, so careful references preserve the hash rather than relying on the height alone. A height is useful context, not a globally unique block identifier.
When recording a payment observation, keep its containing block reference alongside the transaction ID. This makes it easier to compare sources and understand a later change in confirmation status.
Read timestamps and labels carefully
A displayed block timestamp is not a receipt showing precisely when a user pressed Send. Broadcasting, inclusion, observation, and business account credit can have different times. Do not combine them into a single event without knowing what the field represents.
Explorer labels can also involve interpretation. A pool attribution or visual grouping is not proof of every participant’s identity. Separate the underlying field from the provider’s explanation or inference.
Follow a transaction through its block
Choose a confirmed transaction in an external explorer. Open the containing block, locate the transaction in the list, and compare the full identifier. You have checked a relationship between records rather than relying solely on a confirmation badge.
For confirmation arithmetic, read the mempool, confirmations, and fees guide. For the relationship between validation and presentation, read explorer vs. wallet vs. node. No block figures on this site are presented as live network measurements.