Key takeaways
- Super Representatives produce a block every 3 seconds. A new block is on the chain immediately, but it is not yet irreversible.
- A block becomes solidified — permanently confirmed — once at least 70% of the 27 Super Representatives have built on it: 18 later blocks from 18 different producers, plus the original, is 19 confirmations.
- That takes about 54 seconds. Until it happens, the block sits in a reversible window where a longer competing chain could still displace it.
- The solidified block lags the chain head by roughly 19 blocks, and it is the frontier of what is safe to treat as final.
A transaction confirmed on many chains is a matter of degree — one confirmation, six confirmations, more is safer. TRON draws a harder line. A block is either solidified, meaning it can never be reversed, or it is not, meaning in principle it still can. The distance from the newest block to that line is short — under a minute — but reading a transaction as settled before it crosses is one of the easier ways to be wrong about the chain.
This article is about where the line sits and how a block reaches it. The block producers themselves — who they are, how they are elected — are the subject of DPoS and the 27; here the concern is narrower: how a produced block becomes an irreversible one, and what the gap between the two means for anything you read.
Blocks arrive every three seconds
Production rotates among the Super Representatives. When a producer’s slot comes up, it packages pending transactions into a block and appends it to the chain, and that block is on-chain the moment it propagates. The pace is fixed at one block every 3 seconds.
Finality comes later. The freshly produced block is the newest link in the chain and also the least certain one: it has been created by a single producer and not yet ratified by the others. Its transactions can be read immediately, but nothing yet guarantees they will stay.
Solidification: when a block becomes irreversible
The rule is a supermajority. A block becomes solidified once it is “acknowledged by at least 70% of the SRs,” and with 27 producers, 70% is about 19. Acknowledgment is not a vote message; it is the act of building. An SR acknowledges a block by producing a later block on the chain that contains it. So a block solidifies once 18 subsequent blocks have been produced by 18 different Super Representatives which, counted together with the block’s own producer, is 19 distinct confirmations. At that point its transactions are “permanently confirmed by the entire network.”
The strength of the rule sits in the word distinct. A single dishonest producer, or a few, cannot manufacture finality by stacking blocks; the count only advances when a new, different SR builds on the block, so reaching 19 means a supermajority of the independently elected producers has extended this particular history.
The reversible window
Until a block solidifies, it can still be undone. TRON resolves competing histories by the longest-chain principle: when two branches exist, the network follows the one with more blocks. A transaction sitting in a just-produced block is on the branch that is currently longest, but a different branch could overtake it before it solidifies, and if that happens, the transaction returns to pending as though it had never been included. This stretch between the chain head and the solidified point is the reversible window: the record there is real but not yet guaranteed.
The window is short. At one block every 3 seconds and roughly 19 blocks to finality, the arithmetic works out to about 54 seconds — the documentation gives it as 27 × 2/3 × 3. Under a minute after a transaction is included, in normal operation, it has passed the line and cannot be reversed.
One scheduled pause interrupts the rhythm. Every six-hour epoch includes a short maintenance period, a couple of slots in which the network tallies votes and reselects the top 27 producers for the next round. Block production halts for those slots and resumes once the new roster is set.
What this means for a reader
Most of this cashes out in how you treat a fresh transaction.
A recent block is not proof. A transaction in the newest few blocks is on-chain, but it has not solidified, and until it does the honest description is “included but not yet final.” Treating it as settled skips that step.
The solidified block number is the safe frontier. Everything at or below the latest solidified block is irreversible; everything above it is still in the window. That number, not the chain head, is the right reference for a finding meant to stand.
The wait itself is about 54 seconds, roughly 19 blocks. For watching activity, the head is fine; for recording something as fact, the solidified point is the one to read, and the network exposes a separate solidified data surface to serve it.
A block’s place in the chain says only that it was produced. Whether its contents can still be taken back depends on where it sits relative to the solidified line, and a transaction becomes a permanent part of the record only once it has passed it.
Sources
- TRON DPoS Consensus Mechanism — java-tron documentation — the solidified (irreversible) block rule: acknowledgment by at least 70% of the 27 SRs (≈19), acknowledgment as producing a subsequent block, the ~54-second confirmation time (27 × 2/3 × 3 at one block per 3 seconds), the six-hour epoch (“TRON defines every 6 hours as an epoch”), and the maintenance period at each epoch boundary that tallies votes and re-elects the 27 SRs while block production skips 2 slots.
- Consensus — TRON Developer Hub — block production every 3 seconds by the elected Super Representatives and the longest-chain rule for resolving competing branches.
- Blocks — TRON Developer Hub — block structure and the solidified-block concept as the confirmed, irreversible frontier of the chain.