JSON RPC API -3
JSON RPC API Deprecated Methods
getConfirmedBlock
DEPRECATED: Please use getBlock instead This method is expected to be removed in put-core v2.0
Returns identity and transaction information about a confirmed block in the ledger
Parameters:#
<u64> - slot, as u64 integer
(optional) <object> - Configuration object containing the following optional fields:
(optional) encoding: <string> - encoding for each returned Transaction, either "json", "jsonParsed", "base58" (slow), "base64". If parameter not provided, the default encoding is "json". "jsonParsed" encoding attempts to use program-specific instruction parsers to return more human-readable and explicit data in the transaction.message.instructions list. If "jsonParsed" is requested but a parser cannot be found, the instruction falls back to regular JSON encoding (accounts, data, and programIdIndex fields).
(optional) transactionDetails: <string> - level of transaction detail to return, either "full", "signatures", or "none". If parameter not provided, the default detail level is "full".
(optional) rewards: bool - whether to populate the rewards array. If parameter not provided, the default includes rewards.
(optional) commitment: <string> - Commitment; "processed" is not supported. If parameter not provided, the default is "finalized".Results:#
The result field will be an object with the following fields:
<null> - if specified block is not confirmed
<object> - if block is confirmed, an object with the following fields:
blockhash: <string> - the blockhash of this block, as base-58 encoded string
previousBlockhash: <string> - the blockhash of this block's parent, as base-58 encoded string; if the parent block is not available due to ledger cleanup, this field will return "11111111111111111111111111111111"
parentSlot: <u64> - the slot index of this block's parent
transactions: <array> - present if "full" transaction details are requested; an array of JSON objects containing:
transaction: <object|[string,encoding]> - Transaction object, either in JSON format or encoded binary data, depending on encoding parameter
meta: <object> - transaction status metadata object, containing null or:
err: <object|null> - Error if transaction failed, null if transaction succeeded. TransactionError definitions
fee: <u64> - fee this transaction was charged, as u64 integer
preBalances: <array> - array of u64 account balances from before the transaction was processed
postBalances: <array> - array of u64 account balances after the transaction was processed
innerInstructions: <array|null> - List of inner instructions or null if inner instruction recording was not enabled during this transaction
preTokenBalances: <array|undefined> - List of token balances from before the transaction was processed or omitted if token balance recording was not yet enabled during this transaction
postTokenBalances: <array|undefined> - List of token balances from after the transaction was processed or omitted if token balance recording was not yet enabled during this transaction
logMessages: <array|null> - array of string log messages or null if log message recording was not enabled during this transaction
DEPRECATED: status: <object> - Transaction status
"Ok": <null> - Transaction was successful
"Err": <ERR> - Transaction failed with TransactionError
signatures: <array> - present if "signatures" are requested for transaction details; an array of signatures strings, corresponding to the transaction order in the block
rewards: <array> - present if rewards are requested; an array of JSON objects containing:
pubkey: <string> - The public key, as base-58 encoded string, of the account that received the reward
lamports: <i64>- number of reward lamports credited or debited by the account, as a i64
postBalance: <u64> - account balance in lamports after the reward was applied
rewardType: <string|undefined> - type of reward: "fee", "rent", "voting", "staking"
commission: <u8|undefined> - vote account commission when the reward was credited, only present for voting and staking rewards
blockTime: <i64|null> - estimated production time, as Unix timestamp (seconds since the Unix epoch). null if not availableExample:#
Request:
Result:
Example:#
Request:
Result:
For more details on returned data: Transaction Structure Inner Instructions Structure Token Balances Structure
getConfirmedBlocks
DEPRECATED: Please use getBlocks instead This method is expected to be removed in put-core v2.0
Returns a list of confirmed blocks between two slots
Parameters:#
Results:#
The result field will be an array of u64 integers listing confirmed blocks between start_slot and either end_slot, if provided, or latest confirmed block, inclusive. Max range allowed is 500,000 slots. Example:#
Request:
Result:
getConfirmedBlocksWithLimit
DEPRECATED: Please use getBlocksWithLimit instead This method is expected to be removed in put-core v2.0
Returns a list of confirmed blocks starting at the given slot
Parameters:#
Results:#
The result field will be an array of u64 integers listing confirmed blocks starting at start_slot for up to limit blocks, inclusive.
Example:#
Request:
Result:
getConfirmedSignaturesForAddress2
DEPRECATED: Please use getSignaturesForAddress instead This method is expected to be removed in put-core v2.0
Returns signatures for confirmed transactions that include the given address in their accountKeys list. Returns signatures backwards in time from the provided signature or most recent confirmed block
Parameters:#
Results:#
The result field will be an array of transaction signature information, ordered from newest to oldest transaction:
Example:#
Request:
Result:
getConfirmedTransaction
DEPRECATED: Please use getTransaction instead This method is expected to be removed in put-core v2.0
Returns transaction details for a confirmed transaction Parameters:#
Results:#
Example:#
Request:
Result:
Example:#
Request:
Result:
getFeeCalculatorForBlockhash
DEPRECATED: Please use isBlockhashValid or getFeeForMessage instead This method is expected to be removed in put-core v2.0
Returns the fee calculator associated with the query blockhash, or null if the blockhash has expired
Parameters:#
Results:#
The result will be an RpcResponse JSON object with value equal to:
Example:#
Request:
Result:
getFeeRateGovernor
Returns the fee rate governor information from the root bank
Parameters:#
None Results:#
The result field will be an object with the following fields:
Example:#
Request:
Result:
getFees
DEPRECATED: Please use getFeeForMessage instead This method is expected to be removed in put-core v2.0
Returns a recent block hash from the ledger, a fee schedule that can be used to compute the cost of submitting a transaction using it, and the last slot in which the blockhash will be valid. Parameters:#
Results:#
The result will be an RpcResponse JSON object with value set to a JSON object with the following fields:
Example:#
Request:
Result:
getRecentBlockhash
DEPRECATED: Please use getLatestBlockhash instead This method is expected to be removed in put-core v2.0
Returns a recent block hash from the ledger, and a fee schedule that can be used to compute the cost of submitting a transaction using it. Parameters:#
Results:#
An RpcResponse containing a JSON object consisting of a string blockhash and FeeCalculator JSON object.
Example:#
Request:
Result:
getSnapshotSlot
DEPRECATED: Please use getHighestSnapshotSlot instead This method is expected to be removed in put-core v2.0
Returns the highest slot that the node has a snapshot for
Parameters:#
None
Results:#
Example:#
Request:
Result:
Result when the node has no snapshot:
Last updated