Recognize a reproposed Tenderbake payload
A later-round Tezos block can reuse a payload proposed in an earlier round. Counting every proposal as new transaction content overstates activity during a slow level.
Compare the proposal and payload rounds
Set BLOCK to a known block hash. Inspect the payload_hash and payload_round in its header. Obtain the block round using tooling that decodes the protocol’s fitness format at that level.
octez-client rpc get "/chains/main/blocks/$BLOCK/header"
Suppose the block round is 2 and payload_round is 0. The payload originated in round 0 and was reproposed. Preserve the level, round and block hash when distinguishing header proposals; use the payload identity when comparing their transaction content.
Keep observation limits explicit
The canonical block alone does not enumerate every competing or abandoned proposal seen by bakers. To reconstruct timing across rounds, retain consensus observations or baker logs collected during the incident. octez.tezos.com Octez protocol documentation