POSTblock_effects
https://near-mainnet.nodit.io/Returns, by change type, the accounts whose state changed in a block. Each item holds only the change type (type) and the account ID. Query the changed values with the changes method.
Use finality for the latest block, or block_id (block height or block hash) for a specific block. The result list is under the changes key. If the block cannot be found, the UNKNOWN_BLOCK error is returned. EXPERIMENTAL_changes_in_block is the former name of this method.
Request ID. Any string; it is returned unchanged in the response.
Specifies the block finality. Cannot be used together with block_id.
optimistic: the latest block the node has received (may be reorganized)near-final: a Doomslug-final block (not reverted in most cases)final: a fully finalized block
Specifies the block to query by block height (integer) or block hash (base58 string).
Cannot be used together with finality.
Block selector. genesis returns the genesis block; earliest_available returns the oldest block the node holds.
JSON-RPC version
Request ID
Hash of the queried block (base58)
Accounts whose state changed. An account appears per change type, and may repeat as many times as the same kind of change occurred.
Change type
account_touched: account info (balance, locked amount, storage usage, code hash) changed, or the account was deletedaccess_key_touched: an access key was added, changed, or deleteddata_touched: contract storage data was changed or deletedcontract_code_touched: contract code was deployed or deleted
Account ID whose state changed
Error class. REQUEST_VALIDATION_ERROR (invalid request), HANDLER_ERROR (processing error), INTERNAL_ERROR (node internal error)
The specific cause of the error.
Name of the error cause (e.g. UNKNOWN_BLOCK, UNKNOWN_ACCOUNT, PARSE_ERROR)
Additional information about the error (block hash, height, account ID, etc.)
Legacy JSON-RPC error code (e.g. -32000 server error, -32700 parse error, -32601 method not found)
Legacy error message
Legacy error details