Network Explorer

TRON

TRX · Account-based blockchain

A high-throughput blockchain secured by delegated proof of stake and Super Representatives.

Open TRONSCAN

Latest from the chain

Recent blocks, validated ledgers and current fees, read from public nodes. Updates on its own while this page is open.

Delayed via TronGrid Updated 1 h 15 min ago
Latest block
#87,913,62000000000…9bede5
Produced
1 h 15 min agoavg 3 s per block, last 2
Transactions
520avg 504 per block, last 3
Energy price
100 SUNper unit of energy · bandwidth 1,000 SUN per byte
ThroughputMeasuring…needs about a minute of blocks in a row
  1. #87,913,62000000000…9bede5TGyrSc…ewJ9520 transactions1 h 15 min ago
  2. #87,913,61900000000…529a5aTTMNxT…ga7j515 transactions1 h 15 min ago
  3. #87,913,61800000000…9d67daTVFKwz…AWaA478 transactions1 h 15 min ago

Select any height to see its details here. Read-only data from public nodes, shared by all visitors and cached for a few seconds. Full history on TRONSCAN.

Over time

Hourly averages this site collects from public nodes while it runs, so the chart grows longer every day.

100 SUN per energyFee · average 100 SUN per energy · low 100 SUN per energy · high 100 SUN per energy
Fee on TRX from 10 Nov, 15:00 to 11 Nov, 15:00 UTC: average 100 SUN per energy, low 100 SUN per energy, high 100 SUN per energy.

What will it cost?

Estimate a transaction fee from the network's current rates. Real fees depend on your wallet and the exact transaction.

Free≈ < $0.01No energy needed · bandwidth from your free daily allowance

Staking TRX for energy or bandwidth can make transactions free. Every account gets some free bandwidth each day.

Network profile

Consensus, record structure and settlement. Switch networks from the bar above.

TRONDelegated proof of stake · ~3 seconds
TRX

How it operates

TRON uses a rotating set of Super Representatives to produce blocks. Transactions consume network resources, particularly bandwidth and energy, and may require TRX when resources are insufficient.

Data model
Account-based blockchain
Native unit
TRX
Network fee
Bandwidth / energy; fee in SUN
Address format
Base58 addresses generally begin with T
Programmability
TVM smart contracts (EVM-compatible)
Supply
No fixed cap; fees paid in TRX are burned
Unit converter1 TRX = 1,000,000 SUN

What a record contains

Core protocol fields describe the contents, ordering and execution of a transaction.

TRX transaction6 fields
  1. Contract typeThe action performed, such as TransferContract or TriggerSmartContract.
  2. ref_block_bytesTwo bytes of a recent block height; with ref_block_hash it anchors the transaction to the chain.
  3. ExpirationDeadline after which the transaction can no longer be included.
  4. BandwidthConsumed per byte of transaction data, from free or staked allowance or by burning TRX.
  5. EnergyConsumed by smart-contract execution, from staked TRX or by burning TRX.
  6. fee_limitMost TRX, in SUN, a smart-contract call may burn for energy; not used by plain transfers.
Confirmation & settlement

Block inclusion and block solidification are separate concepts. Confirmation and irreversibility depend on subsequent chain progress.

Networks, compared

The same questions, answered for each network. Select a column to open its profile.

Comparison of XRP, TRX, ETH, BTC
Property
ConsensusXRPL Consensus ProtocolDelegated proof of stakeProof of stakeProof of work
Block / ledger interval~3–5 seconds~3 seconds12-second slots~10 minutes
Typical pace≈15 per minute≈20 per minute≈5 per minute≈6 per hour
Data modelAccount-based ledgerAccount-based blockchainAccount / EVMUTXO
Network feeDrops (1 XRP = 1,000,000 drops)Bandwidth / energy; fee in SUNGas × price (gwei); paid in ETHSatoshis per virtual byte (sat/vB)
SettlementValidated ledgerBlock solidificationEpoch-based finalityBlock confirmations
Typical finality~3–5 s (one validated ledger)~1 min (solidified after 19 blocks)~13 min (two epochs)~60 min (6 confirmations, by convention)
ProgrammabilityBuilt-in transaction types (payments, DEX, AMM, escrow)TVM smart contracts (EVM-compatible)EVM smart contractsBitcoin Script (deliberately limited)
Supply100 billion created at launch; fees are destroyedNo fixed cap; fees paid in TRX are burnedNo fixed cap; base fees are burnedCapped at 21 million BTC

Different networks, different rules

Every protocol has its own approach to ordering transactions and defining settlement.

Consensus

Validators or miners determine which data becomes part of the agreed chain or ledger.

On XRP LedgerXRPL Consensus Protocol

On TRONDelegated proof of stake

On EthereumProof of stake

On BitcoinProof of work

Transaction structure

Inputs, outputs, accounts, nonces, signatures and execution resources vary by network.

On XRP LedgerAccount-based ledger

On TRONAccount-based blockchain

On EthereumAccount / EVM

On BitcoinUTXO

Settlement

Block inclusion, validations and finality represent different degrees of confidence.

On XRP LedgerValidated ledger

On TRONBlock solidification

On EthereumEpoch-based finality

On BitcoinBlock confirmations

Read the data

Common concepts you encounter while exploring blockchain records.

9 terms · answers follow the selected network

A canonical unit containing transactions or the resulting accepted state, depending on protocol.

On XRP Ledger, look forLedger index

On TRON, look forBlock number

On Ethereum, look forBlock number

On Bitcoin, look forBlock height

An identifier derived from transaction data that can be used to find a record.

On XRP Ledger, a hash is64 hexadecimal characters

On TRON, a hash is64 hexadecimal characters

On Ethereum, a hash is0x followed by 64 hexadecimal characters

On Bitcoin, a hash is64 hexadecimal characters (txid)

The public identifier that receives funds or controls an account; its format is specific to each network.

On XRP LedgerClassic addresses generally begin with r

On TRONBase58 addresses generally begin with T

On Ethereum20-byte addresses generally written as 0x…

On BitcoinCommon prefixes: bc1, 1 and 3

The amount charged for processing, computation or block space; calculation differs by protocol.

On XRP LedgerDrops (1 XRP = 1,000,000 drops)

On TRONBandwidth / energy; fee in SUN

On EthereumGas × price (gwei); paid in ETH

On BitcoinSatoshis per virtual byte (sat/vB)

Amounts are recorded as whole numbers of a base unit; the familiar coin amount is a decimal view of it.

On XRP Ledger1 XRP = 1,000,000 drops

On TRON1 TRX = 1,000,000 SUN

On Ethereum1 ETH = 10⁹ Gwei = 10¹⁸ Wei

On Bitcoin1 BTC = 100,000,000 sat

How a network keeps a signed transaction from being applied twice or out of order.

On XRP LedgerAccount Sequence (or Ticket)

On TRONReference block + expiration

On EthereumAccount nonce

On BitcoinEach output is spent once

A signed transaction that nodes have received but not yet included in a block or validated ledger.

On XRP Ledger, it waits in theOpen ledger and transaction queue

On TRON, it waits in thePending pool on each node

On Ethereum, it waits in thePublic mempool (txpool)

On Bitcoin, it waits in theMempool

Evidence of inclusion or validation; stronger settlement conditions differ between networks.

On XRP LedgerValidated ledger

On TRONBlock solidification

On EthereumEpoch-based finality

On BitcoinBlock confirmations

The point after which a recorded transaction is treated as permanent; how it is reached, and how long it takes, depends on the protocol.

On XRP Ledger, typically~3–5 s (one validated ledger)

On TRON, typically~1 min (solidified after 19 blocks)

On Ethereum, typically~13 min (two epochs)

On Bitcoin, typically~60 min (6 confirmations, by convention)