Given a range query parameter return an array of all the blocks within that range.
A range of integers. There is a max limit of 500 blocks per request.
0-499
When set to true
, every event will have an extra docs
property with a string of the events documentation.
false
When set to true
, every extrinsic will have an extra docs
property with a string of the extrinsics documentation.
false
When set to true
, the fee won't be calculated for the extrinsics.
false
Note: Block finalization does not correspond to consensus, i.e. whether the block is in the canonical chain. It denotes the finalization of block construction.
Returns a single block. BlockId can either be a block hash or a block height. Replaces /block/{number}
from versions < v1.0.0.
Block identifier, as the block height or block hash.
^0[xX][0-9a-fA-F]{1,64}$|[0-9]{1,12}
When set to true
, every event will have an extra docs
property with a string of the events documentation.
false
When set to true
, every extrinsic will have an extra docs
property with a string of the extrinsics documentation.
false
When set to true
, the fee won't be calculated for the extrinsics.
false
When set to false, this will override the chain-config, and omit the finalized key in the response. This can increase performance slightly by avoiding an additional RPC call to the node.
When set to true
, this will show the decoded XCM messages within the extrinsics of the requested block.
false
When it is set, this will return only the decoded XCM messages for the specified origin Parachain Id (originParaId). To activate this functionality, ensure that the decodedXcmMsgs
parameter is set to true.
Block information that includes the decoded XCM messages if any are found in the queried block. If not, the decodedXcmMsgs object will be returned with three empty arrays corresponding to each direction, horizontalMessages, downwardMessages, upwardMessages.
Note: Block finalization does not correspond to consensus, i.e. whether the block is in the canonical chain. It denotes the finalization of block construction.
Object with three arrays, one for every XCM direction. The arrays are populated or left empty based on the direction of the current XCM message that is being decoded. The XCM messages can be Upward and/or Horizontal (in transit
) messages when connected to a Relay chain. When connected to a Parachain, the messages can be Downward and/or Horizontal. One or more messages can be present in a single block. In case of multiple messages from the same paraIds (originParaId and/or destinationParaId), the messages will be shown under the field data
.