| blocks | Blocks are the building blocks of blockchains and rollups. A block contains transactions which will alter the state of an EVM system incrementally. Transaction within a block can only be executed one after the other, not in parallel. |
| transactions | Transactions are cryptographically signed instructions from accounts. An account will initiate a transaction to update the state of the blockchain network. Transactions always originate from an externally owned account (a smart contract can not initiate a transaction). Transactions, which change the state of the EVM, need to be broadcast to the whole network. Any node can broadcast a request for a transaction to be executed on the EVM; after this happens, a validator will execute the transaction and propagate the resulting state change to the rest of the network. |
| logs | Logs (or event logs), is a way for smart contracts to communicate with the outside world by “documenting” small pieces of information. Event logs allow other people to know that something has happened without them having to query the contract directly. The most common form of event logs today are TRC20 token transfer events. |
| contracts | Contracts are the smart contracts deployed on the blockchain. |
| traces_native | Trace calls, or internal transaction data from Tron’s native API call. Internal Transactions represent all transactions that happen in a smart contract call. Some important information is included in the transaction, such as the sender/receiver address in a token/trx transfer transaction, trx/token amount, transfer status, etc. |
| transactions_native | Native tron transactions and internal transactions from Tron’s native API. |
| trc10_tokens | TRC10 tokens metadata. |
| trc20_tokens | TRC20 tokens metadata. |
| trc721_tokens | TRC721 tokens metadata. |
| trc1155_tokens | TRC1155 tokens metadata. |
