In a blockchain, a block is a collection of verified transactions that are bundled together and added to the blockchain in sequential order. Each block contains a block header and block data. The block header contains metadata about the block, such as a timestamp, a unique identifier (known as a "hash"), and a reference to the previous block in the chain. This reference to the previous block creates a chronological link between blocks and helps ensure the integrity of the blockchain.

The data in a block is the actual set of transactions that are being added to the blockchain. These transactions include things like sending cryptocurrency from one wallet to another, executing a smart contract, or adding a new asset/token to the blockchain. The block data is represented as a digital ledger, which includes information about the sender, receiver, asset amount(s), and other relevant details. Once a block is added to the blockchain, it becomes a permanent and unalterable record that can be verified by anyone on the network.


The specific block data that Amberdata offers depends on the blockchain network, but some examples of the data we have include:

  • Block details: Information about each block in a blockchain network, including its hash, timestamp, size, and transaction data.

  • Transaction data: Detailed information about transactions in a blockchain network, including sender and receiver addresses, gas used, and transaction fees.

  • Token data: Data on tokens in a blockchain network, including token balances, supply, and transaction history.

  • Contract data: For smart contract-based blockchains, we offer data on the contracts themselves, including contract address, source code, and contract events.

  • Address data: Data on addresses in a blockchain network, including balances, transaction history, and token holdings.

  • Network data: Data on various network metrics, such as network hash rate, difficulty, and mining rewards.

Overall, Amberdata provides a wealth of data for blockchain developers and businesses looking to analyze and understand blockchain networks.

API Endpoints

/blocks single
/blocks all
/blocks functions & logs; functions
/blocks functions & logs; logs
/blocks metrics latest
/blocks metrics historical
/blocks tokens transfers
/blocks transactions


Our Blockchain endpoints found throughout the different On-Chain namespaces are available via REST API, WebSockets or JSON RPC. The list of supported Blockchain networks can be found in the API Documentation here.

Since we maintain our own nodes, we have every event from the genesis block forward which enables us to provide complete historical datasets for most of the chains we support.

Frequently Asked Questions

What is the value of showing block data compared to address and transaction data?

  • By allowing you to query block data in addition to address and transaction data, we give you the choice with how granular to query the data. If you need a high level view of transaction data, using the block transactions endpoint makes sense as opposed to the more granular transactions hash endpoint.