Blockchain Nonce Glossary
Concise definitions for the fields, outputs, queues, and security concepts used throughout our nonce guides.
Block header
A compact data structure that commits to a block’s position, transaction set, time-related data, target, and proof-of-work inputs.
Block nonce
A field miners can vary in a proof-of-work block header to produce a different candidate hash.
Difficulty
A human-readable expression of how restrictive a proof-of-work target is relative to a reference target.
Double-spend
An attempt to use the same spendable value in conflicting transactions. Consensus determines the accepted history.
Extra nonce
Miner-controlled coinbase data used to create additional Merkle roots and block-header search space beyond the 32-bit header nonce.
Hash
A fixed-length output produced by a hash function from an input. Small input changes normally produce very different outputs.
Mempool
A node’s local collection of valid unconfirmed transactions. Mempools can differ between nodes.
Merkle root
A compact commitment in a block header derived from the block’s transaction identifiers.
Nonce
A value intended to be unique in a defined context. It may be a search variable, sequence counter, random challenge, or protocol-specific one-time value.
Proof-of-work
A consensus component in which producing a qualifying hash requires repeated computation while verification remains comparatively cheap.
Replay attack
Reusing a previously valid signed or authenticated message in a context where the system mistakenly accepts it again.
Target
The maximum numeric hash value accepted for a proof-of-work candidate. A lower target is harder to meet.
Transaction nonce
A sequence number attached to an account’s outgoing transaction, used for ordering and reuse prevention.