Skip to main content

/v1/blocks/by_version/{version} REST API Endpoint

Retrieves a specific block's information from the Aptos blockchain network, given its version number.

Updated on
Oct 4, 2023

/v1/blocks/by_version/{version} REST API Endpoint

Path Parameters

version
integer
REQUIRED
The ledger version to retrieve the block information

Query Parameters

with_transactions
boolean
When set to true, all transactions are included in the block; otherwise, if not provided or set to false, no transactions will be retrieved

Returns

block_height
The height of the block
block_hash
The hash of the block at the specified height
block_timestamp
The time at which the block was created/added to the chain
first_version
The version number of the first transaction in the block
last_version
The version number of the last transaction in the block
transactions
An array containing the details of the transactions included in the block:
type
The type of the change
hash
The hash of the transaction
sender
The account from which the transaction was sent
sequence_number
The sequence of a transaction sent by the specific sender
max_gas_amount
The maximum amount of gas allocated for the execution of a transaction
gas_unit_price
The cost per unit of gas, determining the transaction fee paid by the sender for each unit of computational resource consumed
expiration_timestamp_secs
The timestamp indicating the expiration period of a transaction, specifying the time until which the transaction can be included in a block
payload
The data that is being carried by a transaction. It contains the following fields:
type
The type of payload indicating the purpose of the data contained
function
The function associated with the payload
type_arguments
An array specifying the types of arguments provided to the function
arguments
An array containing the actual arguments passed to the function
signature
An array with the following fields:
type
The type of signature used to verify the authenticity of the function
public_key
The public key associated with the account that generated the signature, used for verifying the signature's validity
signature
The actual signature generated using the private key corresponding to the public key provided
Request
1
curl -X 'GET' 'https://docs-demo.aptos-mainnet.quiknode.pro/v1/blocks/by_version/3?with_transactions=true' \
2
    -H 'Content-Type: application/json'
Don't have an account yet?
Create your QuickNode endpoint in seconds and start building
Get started for free