Live Tron Mempool

The mempool (memory pool) is the queue of pending transactions a node holds before they're sealed into a block. Each Tron node maintains its own copy; the figures on this page reflect the queue on the node powering Tron Goblin. On Tron, blocks arrive every ~3 seconds and most transactions live in the mempool for less than 2 seconds — much shorter than other chains.

Every ~2.5 seconds the server polls a Tron node's /wallet/getpendingsize and /wallet/gettransactionlistfrompending endpoints, diffs the result against the last poll to identify newly arrived transactions, fetches a sample of their decoded bodies, and pushes a snapshot to every connected browser via Server-Sent Events. No third-party feed; this is the raw queue state.

Mempools are local. A transaction broadcast to the network propagates peer-to-peer, so different nodes see it at slightly different moments. They also expire from each node's pool independently once included in a block (or after a configurable timeout). Two nodes a few seconds apart in connectivity will report different pending counts even on the same chain.

Dwell time is how long a transaction sat in the mempool before it left — either because it was included in a block, or because the node evicted it (typically after the user-set expiration window). On Tron the average dwell is sub-second to a few seconds; longer dwells usually signal a fee-limit problem or a stuck contract.

The live feed surfaces a sample of newly-seen arrivals — typically 20–30 fresh ones per tick. To bound memory and bandwidth we don't pull every single hash's body on every poll; the composition stats and pending count cover the whole pool, while the feed shows the freshest activity.

No — the dashboard shows confirmed transactions (already in blocks). This page shows pending transactions — the few seconds of activity before they're confirmed. Same chain, different state.