Get blocks by height

This endpoint allows you to get the transactions in a block and the corresponding block information.

Transactions are limited by max default transactions size. If not all transactions are present, the user will need to query for the rest of the transactions via the get transactions API.

If the block is pruned, it will return a 410

Path Parameters

block_height

integer

required

Block height to lookup. Starts at 0

Query Parameters

with_transactions

boolean

If set to true, include all transactions in the block

If not provided, no transactions will be retrieved

Response

200

application/json

A Block with or without transactions

This contains the information about a transactions along with associated transactions if requested

block_height

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

block_hash

string

required

block_timestamp

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

first_version

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

last_version

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

transactions

object[]

The transactions in the block in sequential order

• Option 1
• Option 2
• Option 3
• Option 4
• Option 5

Show child attributes

transactions.type

string

required

transactions.hash

string

required

transactions.sender

string

required

A hex encoded 32 byte Aptos account address.

This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.

For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.

transactions.sequence_number

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

transactions.max_gas_amount

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

transactions.gas_unit_price

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

transactions.expiration_timestamp_secs

string

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

transactions.payload

object

required

An enum of the possible transaction payloads

• Option 1
• Option 2
• Option 3
• Option 4

Show child attributes

transactions.payload.type

string

required

transactions.payload.function

string

required

Entry function id is string representation of a entry function defined on-chain.

Format: {address}::{module name}::{function name}

Both module name and function name are case-sensitive.

transactions.payload.type_arguments

string[]

required

Type arguments of the function

transactions.payload.arguments

any[]

required

Arguments of the function

transactions.signature

object

An enum representing the different transaction signatures available

• Option 1
• Option 2
• Option 3

Show child attributes

transactions.signature.type

string

required

transactions.signature.public_key

string

required

All bytes (Vec<u8>) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

transactions.signature.signature

string

required

All bytes (Vec<u8>) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.