Why a blockchain takes time to update
A blockchain is not one document that a single computer can edit. Copies are kept by many computers, called nodes, and those nodes must settle on which new entries are valid and in what order. That coordination takes time: a computer proposing a block has to share it, and the network has to check it against the rules before treating it as part of the record.
Agreement is the bottleneck
Different nodes may hear about a proposed block at different moments, or receive competing proposals. A blockchain’s consensus method—the procedure for choosing which proposal to accept—helps the network converge on one history without relying on a central editor. Depending on the system, this can involve substantial computation, communication among participants, or both. The delay is not simply a computer writing data; it is the cost of getting independent machines to accept the same update.
Why link blocks with fingerprints
Each block contains a cryptographic fingerprint, or hash, of its contents and a reference to the previous block’s hash. A hash is a compact value calculated from data; even a small alteration produces a different one. Changing an old entry therefore breaks the link to the next block, and the mismatch can be detected when nodes check the chain.
That structure makes quiet edits conspicuous, but it does not make agreement instantaneous. The network still has to decide which valid history to extend. The tradeoff is deliberate: a shared record can be checked without trusting one keeper, but coordinating updates across many keepers is slower than changing a file on one computer.
