Overview

At Validation Cloud, we understand that every business has unique needs and financial constraints. That’s why we’ve designed our billing system to be as flexible and accommodating as possible, catering to enterprises and experienced developers entering the web3 space. Our pricing model is structured around two primary plans: Free Plan and Scale Plan, charged based on a Compute Unit (CU) system.

Free Plan

Get started with our Node API without any upfront costs or commitment. Simply sign up for free—no credit card required—and gain immediate access to our enterprise-grade nodes with no performance limitations until you've reached your 50 million-th compute unit. Enjoy seamless integration and superior performance up to the 50 millionth compute unit, completely free of charge.

Scale Plan

As your web3 needs grow, Validation Cloud is prepared to scale with you. Our Scale Plan is designed for users requiring additional compute units beyond the Free Plan 50 million CUs. The Scale Plan operates on a sliding scale, with the cost per 1 million CUs decreasing as your usage increases.

In summary, Node API's Scale Plan offers a flexible pricing model that adjusts based on your usage. The more compute units you consume, the lower the cost per million CUs. This approach ensures that you only pay for the resources you need, making it a cost-effective solution for both enterprises and developers at any stage of their web3 venture.

With our Node API, you can trust that you’re getting the most value from your crypto node infrastructure investment. Please feel free to contact us if you have any questions or require further information.

Compute Unit Thresholds

Welcome to the Future of Crypto Node Infrastructure

Enterprises and experienced developers seeking a robust and powerful solution for their web3 needs, look no further. Validation Cloud's Node API is the answer to all your crypto node infrastructure requirements. Our cutting-edge platform offers a comprehensive suite of API endpoints, meticulously categorized by crypto network, to ensure seamless integration and interoperability across the web3 ecosystem.

Our entire platform is engineered to deliver exceptional performance and reliability for your business-critical applications. Our globally resilient infrastructure network employs state-of-the-art Smart Routing technology, which intelligently directs your requests to the closest set of nodes, guaranteeing lightning-fast response times and minimal latency.

Key Features

Extensive API Suite

Our diverse collection of API endpoints caters to a wide range of crypto networks, simplifying your workflow and enabling you to harness the full potential of web3.

Smart Routing

Our Node API's Smart Routing technology ensures optimal performance by selecting the nearest nodes, providing unmatched speed and reliability for your web3 applications.

Enterprise-Grade Security

Validation Cloud adheres to strict security standards, safeguarding your infrastructure and sensitive data while maintaining maximum uptime.

Scalability and Flexibility

Our Node API infrastructure is designed to scale effortlessly with your growing needs, offering unmatched versatility to support your business’s dynamic web3 demands.

24/7 Availability

Our dedicated team of experts is available around the clock to assist you with any technical concerns or queries, ensuring a seamless experience with our infrastructure.

As you explore the limitless possibilities of Validation Cloud's crypto node service, we invite you to familiarize yourself with our competitive and flexible billing options, designed to accommodate businesses of all sizes. In the next section, you’ll find all the information you need to choose the perfect plan for your organization’s unique requirements.

Let’s revolutionize the world of decentralized applications together.

Retrieves all account resources for a given account and a specific ledger version.

This method will use 30 Compute Units.

Retrieves an individual module from a given account and at a specific ledger version.

This method will use 30 Compute Units.

Retrieves an individual resource from a given account and at a specific ledger version.

This method will use 20 Compute Units.

Network Support

Compute Units

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

This method will use 50 .

Returns information about a block by hash.

This method will use 30 Compute Units.

Reference: Here

Parameters

1. DATA, 32 Bytes - Hash of a block.

2. Boolean - If true it returns the full transaction objects, if false only the hashes of the transactions are returned.

params: [
 "0xdc0818cf78f21a8e70579cb46a43643f78291264dda342ae31049421c82d21ae",
 false,
 ]

Returns

Object - A block object, or null when no block was found:

• number: QUANTITY - the block number. null when its pending block.

• hash: DATA, 32 Bytes - hash of the block. null when its pending block.

• parentHash: DATA, 32 Bytes - hash of the parent block.

• nonce: DATA, 8 Bytes - hash of the generated proof-of-work. null when its pending block.

• sha3Uncles: DATA, 32 Bytes - SHA3 of the uncles data in the block.

• logsBloom: DATA, 256 Bytes - the bloom filter for the logs of the block. null when its pending block.

• transactionsRoot: DATA, 32 Bytes - the root of the transaction trie of the block.

• stateRoot: DATA, 32 Bytes - the root of the final state trie of the block.

• receiptsRoot: DATA, 32 Bytes - the root of the receipts trie of the block.

• miner: DATA, 20 Bytes - the address of the beneficiary to whom the mining rewards were given.

• difficulty: QUANTITY - integer of the difficulty for this block.

• totalDifficulty: QUANTITY - integer of the total difficulty of the chain until this block.

• extraData: DATA - the "extra data" field of this block.

• size: QUANTITY - integer the size of this block in bytes.

• gasLimit: QUANTITY - the maximum gas allowed in this block.

• gasUsed: QUANTITY - the total used gas by all transactions in this block.

• timestamp: QUANTITY - the unix timestamp for when the block was collated.

• transactions: Array - Array of transaction objects, or 32 Bytes transaction hashes depending on the last given parameter.

• uncles: Array - Array of uncle hashes.

// Result
{
  "id":83,
  "jsonrpc": "2.0",
  "result": "0x2abfcdcfa71e54e" 
}

curl https://mainnet.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getBlockByHash","params":["0xdc0818cf78f21a8e70579cb46a43643f78291264dda342ae31049421c82d21ae", false],"id":1}'

curl https://sepolia.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getBlockByHash","params":["0x98f37278176977ec9ae5b25ff751bf06f86075b85dd63900c93894b4817256e8", false],"id":1}'

What is a Faucet in web3?

A faucet is a way for web3 users to obtain a small amount of testnet, or sometimes mainnet, tokens to their wallet, for the purpose of getting started using various blockchain networks or protocols, e.g. to help pay initial gas fees for testing transactions.

The name “faucet”, from American English, is used because tokens are usually “dripped” in small amounts over a fixed time period for the same user/wallet, e.g. 100 Test HBAR every 24 hours.

What Faucets does Validation Cloud offer?

We provide testnet faucets for the following networks:

• Berachain bArtio - providing testnet BERA tokens

We also link to other existing testnet faucets for the following networks:

• Aptos

• Casper

• Hedera

• Stellar

Create or log-in to your account, go to Node API at https://app.validationcloud.io/node, select Faucets, and follow the instructions for each network.

Faucet Frequently Asked Questions (FAQ)

Why can I only get X tokens?

Even on testnet networks, tokens need to come from somewhere, often the relevant blockchain foundation.

As a result, individual users/wallets are normally restricted to a certain amount of tokens that provide enough to allow for testing or interaction with the relevant blockchain.

This endpoint returns events emitted to the account matching a given event type.

This method will use 30 Compute Units.

Get the transactions in a block and the corresponding block information given a version in the block.

This method will use 50 Compute Units.

Get the latest ledger information, including data such as chain ID, role type, ledger versions, epoch, etc.

This method will use 10 Compute Units.

Retrieves all account modules' bytecode for a given account at a specific ledger version.

This method will use 60 Compute Units.

Retrieve on-chain committed transactions.

This method will use 150 .

Get a table item at a specific ledger version from the table.

This method will use 150 .

Return the authentication key and the sequence number for an account address.

This method will use 15 .

Get a raw table item at a specific ledger version from the table.

This method will use 200 .

Event types are globally identifiable by an account address and monotonically increasing creation_number. This API returns events corresponding to that event type.

This method will use 30 .

Look up a transaction by its hash.

This method will use 15 Compute Units.

The output of the transaction will have the exact transaction outputs and events that running an actual signed transaction would have.

This method will use 50 Compute Units.

Retrieves on-chain committed transactions from an account.

This method will use 150 Compute Units.

This method will use 3500 Compute Units.

Retrieves a transaction by a given version.

This method will use 15 Compute Units.

Execute the Move function with the given parameters and return its execution result.

This method will use 50 .

Returns a list of addresses owned by client.

This method will use 10 .

Reference:

Parameters

None

Returns

array of data - 20 Bytes - addresses owned by the client

This method will use 15 .

Returns the chain ID used for signing replay-protected transactions.

This method will use 5 Compute Units.

Reference: Here

Parameters

None

Returns

chainId, hexadecimal value as a string representing the integer of the current chain id.

// Result
{
  "id":67,
  "jsonrpc": "2.0",
  "result": "0x1"
}

curl https://mainnet.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":67}'

curl https://sepolia.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":67}'

This endpoint accepts transaction submissions in two formats.

This method will use 350 Compute Units.

Network Support

Compute Units

Returns the number of most recent block.

This method will use 10 .

Reference:

Parameters

None

Returns

INTEGER - Value of the current block number the client is on

Returns information about a block by block number.

This method will use 20 .

Reference:

Parameters

1. QUANTITY|TAG - integer of a block number, or the string "earliest", "latest" or "pending", as in the .

2. Boolean - If true it returns the full transaction objects, if false only the hashes of the transactions.

Returns

Object - A block object, or null when no block was found:

• number: QUANTITY - the block number. null when its pending block.

• hash: DATA, 32 Bytes - hash of the block. null when its pending block.

• parentHash: DATA, 32 Bytes - hash of the parent block.

• nonce: DATA, 8 Bytes - hash of the generated proof-of-work. null when its pending block.

• sha3Uncles: DATA, 32 Bytes - SHA3 of the uncles data in the block.

• logsBloom: DATA, 256 Bytes - the bloom filter for the logs of the block. null when its pending block.

• transactionsRoot: DATA, 32 Bytes - the root of the transaction trie of the block.

• stateRoot: DATA, 32 Bytes - the root of the final state trie of the block.

• receiptsRoot: DATA, 32 Bytes - the root of the receipts trie of the block.

• miner: DATA, 20 Bytes - the address of the beneficiary to whom the mining rewards were given.

• difficulty: QUANTITY - integer of the difficulty for this block.

• totalDifficulty: QUANTITY - integer of the total difficulty of the chain until this block.

• extraData: DATA - the "extra data" field of this block.

• size: QUANTITY - integer the size of this block in bytes.

• gasLimit: QUANTITY - the maximum gas allowed in this block.

• gasUsed: QUANTITY - the total used gas by all transactions in this block.

• timestamp: QUANTITY - the unix timestamp for when the block was collated.

• transactions: Array - Array of transaction objects, or 32 Bytes transaction hashes depending on the last given parameter.

• uncles: Array - Array of uncle hashes.

This method will use 30 .

Returns the current price per gas in wei.

This method will use 20 .

Reference:

Parameters

None

Returns

String - hex string value representing an integer of the current price per gas in WEI.

Returns the balance of the account of given address.

This method will use 20 .

Reference:

Parameters

1. DATA, 20 Bytes - address to check for balance.

2. QUANTITY|TAG - integer block number, or the string "latest", "earliest" or "pending", see the

Returns

INTEGER - Hex value representing integer of the current balance in WEI.

Generates and returns an estimate of how much gas is necessary to allow the transaction to complete.

This method will use 100 .

Reference:

Parameters

from - [optional] String of the address the transaction is sent from.

to - [optional] String of the address the transaction is directed to.

gas - [optional] Integer of the gas provided for the transaction execution.

gasprice - [optional] Integer of the gasPrice used for each paid gas encoded as a hexadecimal.

value - [optional] Integer of the value sent with this transaction encoded as a hexadecimal.

data - [optional] String of the hash of the method signature and encoded parameters. For more information, see the .

Returns

String - hex string value representing an integer of the amount of gas units used.

Returns the number of transactions in a block matching the given block number.

This method will use 20 Compute Units.

Reference: Here

Parameters

QUANTITY|TAG - integer of a block number, or the string "earliest", "latest" or "pending", as in the default block parameter.

params: [
  "0xe8", // 232
]

Returns

QUANTITY - integer of the number of transactions in this block.

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0xa" // 10
}

curl https://mainnet.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getBlockTransactionCountByNumber","params":["0x55946fd"],"id":1}'

curl https://sepolia.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getBlockTransactionCountByNumber","params":["0xe8"],"id":1}'

Returns an array of all logs matching filter with given id.

This method will use 70 Compute Units.

Reference: Here

Parameters

QUANTITY - the filter id.

params: 
[
  "0x16", // 22
]

Returns

Array - Array of log objects, or an empty array if nothing has changed since last poll.

• For filters created with eth_newBlockFilter the return are block hashes (DATA, 32 Bytes), e.g. ["0x3454645634534..."].

• For filters created with eth_newPendingTransactionFilter the return are transaction hashes (DATA, 32 Bytes), e.g. ["0x6345343454645..."].

• For filters created with eth_newFilter logs are objects with following params:

  • removed: TAG - true when the log was removed, due to a chain reorganization. false if its a valid log.

  • logIndex: QUANTITY - integer of the log index position in the block. null when its pending log.

  • transactionIndex: QUANTITY - integer of the transactions index position log was created from. null when its pending log.

  • transactionHash: DATA, 32 Bytes - hash of the transactions this log was created from. null when its pending log.

  • blockHash: DATA, 32 Bytes - hash of the block where this log was in. null when its pending. null when its pending log.

  • blockNumber: QUANTITY - the block number where this log was in. null when its pending. null when its pending log.

  • address: DATA, 20 Bytes - address from which this log originated.

  • data: DATA - contains one or more 32 Bytes non-indexed arguments of the log.

  • topics: Array of DATA - Array of 0 to 4 32 Bytes DATA of indexed log arguments. (In solidity: The first topic is the hash of the signature of the event (e.g. Deposit(address,bytes32,uint256)), except you declared the event with the anonymous specifier.)

// Result
{
  "id":1,
  "jsonrpc":"2.0",
  "result": [{
    "logIndex": "0x1", // 1
    "blockNumber":"0x1b4", // 436
    "blockHash": "0x8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcfdf829c5a142f1fccd7d",
    "transactionHash":  "0xdf829c5a142f1fccd7d8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcf",
    "transactionIndex": "0x0", // 0
    "address": "0x16c5785ac562ff41e2dcfdf829c5a142f1fccd7d",
    "data":"0x0000000000000000000000000000000000000000000000000000000000000000",
    "topics": ["0x59ebeb90bc63057b6515673c3ecf9438e5058bca0f92585014eced636878c9a5"]
    },{
      ...
    }]
}

curl https://mainnet.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getFilterLogs","params":["0x16"],"id":74}'

curl https://sepolia.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getFilterLogs","params":["0x16"],"id":74}'

Returns an array of all logs matching a given filter object.

This method will use 80 Compute Units.

Reference: Here

Parameters

1. Object - The filter options:

• fromBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.

• toBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.

• address: DATA|Array, 20 Bytes - (optional) Contract address or a list of addresses from which logs should originate.

• topics: Array of DATA, - (optional) Array of 32 Bytes DATA topics. Topics are order-dependent. Each topic can also be an array of DATA with "or" options.

• blockhash: DATA, 32 Bytes - (optional, future) With the addition of EIP-234, blockHash will be a new filter option which restricts the logs returned to the single block with the 32-byte hash blockHash. Using blockHash is equivalent to fromBlock = toBlock = the block number with hash blockHash. If blockHash is present in in the filter criteria, then neither fromBlock nor toBlock are allowed.

params: [
  {
    topics: [
      "0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b",
    ],
  },
]

Returns

See eth_getFilterChanges:

Array - Array of log objects, or an empty array if nothing has changed since last poll.

• For filters created with eth_newBlockFilter the return are block hashes (DATA, 32 Bytes), e.g. ["0x3454645634534..."].

• For filters created with eth_newPendingTransactionFilter the return are transaction hashes (DATA, 32 Bytes), e.g. ["0x6345343454645..."].

• For filters created with eth_newFilter logs are objects with following params:

  • removed: TAG - true when the log was removed, due to a chain reorganization. false if its a valid log.

  • logIndex: QUANTITY - integer of the log index position in the block. null when its pending log.

  • transactionIndex: QUANTITY - integer of the transactions index position log was created from. null when its pending log.

  • transactionHash: DATA, 32 Bytes - hash of the transactions this log was created from. null when its pending log.

  • blockHash: DATA, 32 Bytes - hash of the block where this log was in. null when its pending. null when its pending log.

  • blockNumber: QUANTITY - the block number where this log was in. null when its pending. null when its pending log.

  • address: DATA, 20 Bytes - address from which this log originated.

  • data: DATA - contains one or more 32 Bytes non-indexed arguments of the log.

  • topics: Array of DATA - Array of 0 to 4 32 Bytes DATA of indexed log arguments. (In solidity: The first topic is the hash of the signature of the event (e.g. Deposit(address,bytes32,uint256)), except you declared the event with the anonymous specifier.)

// Result
{
  "id":1,
  "jsonrpc":"2.0",
  "result": [{
    "logIndex": "0x1", // 1
    "blockNumber":"0x1b4", // 436
    "blockHash": "0x8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcfdf829c5a142f1fccd7d",
    "transactionHash":  "0xdf829c5a142f1fccd7d8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcf",
    "transactionIndex": "0x0", // 0
    "address": "0x16c5785ac562ff41e2dcfdf829c5a142f1fccd7d",
    "data":"0x0000000000000000000000000000000000000000000000000000000000000000",
    "topics": ["0x59ebeb90bc63057b6515673c3ecf9438e5058bca0f92585014eced636878c9a5"]
    },{
      ...
    }]
}

curl https://mainnet.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getLogs","params":[{"topics":["0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b"]}],"id":74}'

curl https://sepolia.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getLogs","params":[{"topics":["0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b"]}],"id":74}'

Returns code at a given address.

This method will use 20 Compute Units.

Reference: Here

Parameters

1. DATA, 20 Bytes - address.

2. QUANTITY|TAG - integer block number, or the string "latest", "earliest" or "pending", see the default block parameter

params: [
  "0xa94f5374fce5edbc8e2a8697c15331677e6ebf0b",
  "0x2", // 2
]

Returns

DATA - the code from the given address.

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x600160008035811a818181146012578301005b601b6001356025565b8060005260206000f25b600060078202905091905056"
}

curl https://mainnet.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getCode","params":["0xa94f5374fce5edbc8e2a8697c15331677e6ebf0b", "0x2"],"id":1}'

curl https://sepolia.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getCode","params":["0xa94f5374fce5edbc8e2a8697c15331677e6ebf0b", "0x2"],"id":1}'

Polling method for a filter, which returns an array of logs which occurred since last poll.

This method will use 20 Compute Units.

Reference: Here

Parameters

1. QUANTITY - the filter id.

params: 
[
  "0x16", // 22
]

Returns

Array - Array of log objects, or an empty array if nothing has changed since last poll.

• For filters created with eth_newBlockFilter the return are block hashes (DATA, 32 Bytes), e.g. ["0x3454645634534..."].

• For filters created with eth_newPendingTransactionFilter the return are transaction hashes (DATA, 32 Bytes), e.g. ["0x6345343454645..."].

• For filters created with eth_newFilter logs are objects with following params:

  • removed: TAG - true when the log was removed, due to a chain reorganization. false if its a valid log.

  • logIndex: QUANTITY - integer of the log index position in the block. null when its pending log.

  • transactionIndex: QUANTITY - integer of the transactions index position log was created from. null when its pending log.

  • transactionHash: DATA, 32 Bytes - hash of the transactions this log was created from. null when its pending log.

  • blockHash: DATA, 32 Bytes - hash of the block where this log was in. null when its pending. null when its pending log.

  • blockNumber: QUANTITY - the block number where this log was in. null when its pending. null when its pending log.

  • address: DATA, 20 Bytes - address from which this log originated.

  • data: DATA - contains one or more 32 Bytes non-indexed arguments of the log.

  • topics: Array of DATA - Array of 0 to 4 32 Bytes DATA of indexed log arguments. (In solidity: The first topic is the hash of the signature of the event (e.g. Deposit(address,bytes32,uint256)), except you declared the event with the anonymous specifier.)

// Result
{
  "id":1,
  "jsonrpc":"2.0",
  "result": [{
    "logIndex": "0x1", // 1
    "blockNumber":"0x1b4", // 436
    "blockHash": "0x8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcfdf829c5a142f1fccd7d",
    "transactionHash":  "0xdf829c5a142f1fccd7d8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcf",
    "transactionIndex": "0x0", // 0
    "address": "0x16c5785ac562ff41e2dcfdf829c5a142f1fccd7d",
    "data":"0x0000000000000000000000000000000000000000000000000000000000000000",
    "topics": ["0x59ebeb90bc63057b6515673c3ecf9438e5058bca0f92585014eced636878c9a5"]
    },{
      ...
    }]
}

curl https://mainnet.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getFilterChanges","params":["0x16"],"id":73}'

curl https://sepolia.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getFilterChanges","params":["0x16"],"id":73}'

Returns the receipt of a transaction by transaction hash. Note that the receipt is not available for pending transactions.

This method will use 20 Compute Units.

Reference: Here

Parameters

1. DATA, 32 Bytes - hash of a transaction

params: ["0x85d995eba9763907fdf35cd2034144dd9d53ce32cbec21349d4b12823c6860c5"]

Returns

Object - A transaction receipt object, or null when no receipt was found:

• transactionHash : DATA, 32 Bytes - hash of the transaction.

• transactionIndex: QUANTITY - integer of the transactions index position in the block.

• blockHash: DATA, 32 Bytes - hash of the block where this transaction was in.

• blockNumber: QUANTITY - block number where this transaction was in.

• from: DATA, 20 Bytes - address of the sender.

• to: DATA, 20 Bytes - address of the receiver. null when its a contract creation transaction.

• cumulativeGasUsed : QUANTITY - The total amount of gas used when this transaction was executed in the block.

• effectiveGasPrice : QUANTITY - The sum of the base fee and tip paid per unit of gas.

• gasUsed : QUANTITY - The amount of gas used by this specific transaction alone.

• contractAddress : DATA, 20 Bytes - The contract address created, if the transaction was a contract creation, otherwise null.

• logs: Array - Array of log objects, which this transaction generated.

• logsBloom: DATA, 256 Bytes - Bloom filter for light clients to quickly retrieve related logs.

• type: DATA - integer of the transaction type, 0x00 for legacy transactions, 0x01 for access list types, 0x02 for dynamic fees. It also returns either :

• root : DATA 32 bytes of post-transaction stateroot (pre Byzantium)

• status: QUANTITY either 1 (success) or 0 (failure)

// Result
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "blockHash":
      "0xa957d47df264a31badc3ae823e10ac1d444b098d9b73d204c40426e57f47e8c3",
    "blockNumber": "0xeff35f",
    "contractAddress": null, // string of the address if it was created
    "cumulativeGasUsed": "0xa12515",
    "effectiveGasPrice": "0x5a9c688d4",
    "from": "0x6221a9c005f6e47eb398fd867784cacfdcfff4e7",
    "gasUsed": "0xb4c8",
    "logs": [{
      // logs as returned by getFilterLogs, etc.
    }],
    "logsBloom": "0x00...0", // 256 byte bloom filter
    "status": "0x1",
    "to": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2",
    "transactionHash":
      "0x85d995eba9763907fdf35cd2034144dd9d53ce32cbec21349d4b12823c6860c5",
    "transactionIndex": "0x66",
    "type": "0x2"
  }

curl https://mainnet.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getTransactionReceipt","params":["0x85d995eba9763907fdf35cd2034144dd9d53ce32cbec21349d4b12823c6860c5"],"id":1}'

curl https://sepolia.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getTransactionReceipt","params":["0x85d995eba9763907fdf35cd2034144dd9d53ce32cbec21349d4b12823c6860c5"],"id":1}'

Returns information about a transaction by block hash and transaction index position.

This method will use 20 Compute Units.

Reference: Here

Parameters

1. DATA, 32 Bytes - hash of a block.

2. QUANTITY - integer of the transaction index position.

params: [
  "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331",
  "0x0", // 0
]

Returns

Object - A transaction object, or null when no transaction was found:

• blockHash: DATA, 32 Bytes - hash of the block where this transaction was in. null when its pending.

• blockNumber: QUANTITY - block number where this transaction was in. null when its pending.

• from: DATA, 20 Bytes - address of the sender.

• gas: QUANTITY - gas provided by the sender.

• gasPrice: QUANTITY - gas price provided by the sender in Wei.

• hash: DATA, 32 Bytes - hash of the transaction.

• input: DATA - the data send along with the transaction.

• nonce: QUANTITY - the number of transactions made by the sender prior to this one.

• to: DATA, 20 Bytes - address of the receiver. null when its a contract creation transaction.

• transactionIndex: QUANTITY - integer of the transactions index position in the block. null when its pending.

• value: QUANTITY - value transferred in Wei.

• v: QUANTITY - ECDSA recovery id

• r: QUANTITY - ECDSA signature r

• s: QUANTITY - ECDSA signature s

// Result
{
  "jsonrpc":"2.0",
  "id":1,
  "result":{
    "blockHash":"0x1d59ff54b1eb26b013ce3cb5fc9dab3705b415a67127a003c3e61eb445bb8df2",
    "blockNumber":"0x5daf3b", // 6139707
    "from":"0xa7d9ddbe1f17865597fbd27ec712455208b6b76d",
    "gas":"0xc350", // 50000
    "gasPrice":"0x4a817c800", // 20000000000
    "hash":"0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b",
    "input":"0x68656c6c6f21",
    "nonce":"0x15", // 21
    "to":"0xf02c1c8e6114b1dbe8937a39260b5b0a374432bb",
    "transactionIndex":"0x41", // 65
    "value":"0xf3dbb76162000", // 4290000000000000
    "v":"0x25", // 37
    "r":"0x1b5e176d927f8e9ab405058b2d2457392da3e20f328b16ddabcebc33eaac5fea",
    "s":"0x4ba69724e8f69de52f0125ad8b3c5c2cef33019bac3249e2c0a2192766d1721c"
}

curl https://mainnet.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getTransactionByBlockHashAndIndex","params":["0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b", "0x0"],"id":1}'

curl https://sepolia.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getTransactionByBlockHashAndIndex","params":["0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b", "0x0"],"id":1}'

Executes a new message call immediately without creating a transaction on the block chain.

This method will use 30 Compute Units.

Reference: Here

Parameters

1. Object - The transaction call object

from - [optional] String of the address the transaction is sent from.

to - String of the address the transaction is directed to.

gas - [optional] Integer of the gas provided for the transaction execution.

gasprice - [optional] Integer of the gasPrice used for each paid gas encoded as a hexadecimal.

value - [optional] Integer of the value sent with this transaction encoded as a hexadecimal.

data - [optional] String of the hash of the method signature and encoded parameters. For more information, see the Contract ABI description in the Solidity documentation.

1. QUANTITY | TAG - integer block number, or the string "latest", "earliest" or "pending", see the default block parameter

Returns

data - hex value of the executed call or contract

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x"
}

curl https://mainnet.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"method":"eth_call","params":[{"from":null,"to":"0x6b175474e89094c44da98b954eedeac495271d0f","data":"0x70a082310000000000000000000000006E0d01A76C3Cf4288372a29124A26D4353EE51BE"}, "latest"],"id":1,"jsonrpc":"2.0"}'

curl https://sepolia.arbitrum.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"method":"eth_call","params":[{"from":null,"to":"0x6b175474e89094c44da98b954eedeac495271d0f","data":"0x70a082310000000000000000000000006E0d01A76C3Cf4288372a29124A26D4353EE51BE"}, "latest"],"id":1,"jsonrpc":"2.0"}'

Returns information about a uncle of a block by hash and uncle index position.

This method will use 20 .

Reference:

Parameters

1. DATA, 32 Bytes - The hash of a block.

2. QUANTITY - The uncle's index position.

Returns:

Object - A block object, or null when no block was found:

• number: QUANTITY - the block number. null when its pending block.

• hash: DATA, 32 Bytes - hash of the block. null when its pending block.

• parentHash: DATA, 32 Bytes - hash of the parent block.

• nonce: DATA, 8 Bytes - hash of the generated proof-of-work. null when its pending block.

• sha3Uncles: DATA, 32 Bytes - SHA3 of the uncles data in the block.

• logsBloom: DATA, 256 Bytes - the bloom filter for the logs of the block. null when its pending block.

• transactionsRoot: DATA, 32 Bytes - the root of the transaction trie of the block.

• stateRoot: DATA, 32 Bytes - the root of the final state trie of the block.

• receiptsRoot: DATA, 32 Bytes - the root of the receipts trie of the block.

• miner: DATA, 20 Bytes - the address of the beneficiary to whom the mining rewards were given.

• difficulty: QUANTITY - integer of the difficulty for this block.

• totalDifficulty: QUANTITY - integer of the total difficulty of the chain until this block.

• extraData: DATA - the "extra data" field of this block.

• size: QUANTITY - integer the size of this block in bytes.

• gasLimit: QUANTITY - the maximum gas allowed in this block.

• gasUsed: QUANTITY - the total used gas by all transactions in this block.

• timestamp: QUANTITY - the unix timestamp for when the block was collated.

• transactions: Array - Array of transaction objects, or 32 Bytes transaction hashes depending on the last given parameter.

• uncles: Array - Array of uncle hashes.

Returns information about a transaction by block number and transaction index position.

This method will use 20 .

Reference:

Parameters

1. QUANTITY|TAG - a block number, or the string "earliest", "latest" or "pending", as in the .

2. QUANTITY - the transaction index position.

Returns

Object - A transaction object, or null when no transaction was found:

• blockHash: DATA, 32 Bytes - hash of the block where this transaction was in. null when its pending.

• blockNumber: QUANTITY - block number where this transaction was in. null when its pending.

• from: DATA, 20 Bytes - address of the sender.

• gas: QUANTITY - gas provided by the sender.

• gasPrice: QUANTITY - gas price provided by the sender in Wei.

• hash: DATA, 32 Bytes - hash of the transaction.

• input: DATA - the data send along with the transaction.

• nonce: QUANTITY - the number of transactions made by the sender prior to this one.

• to: DATA, 20 Bytes - address of the receiver. null when its a contract creation transaction.

• transactionIndex: QUANTITY - integer of the transactions index position in the block. null when its pending.

• value: QUANTITY - value transferred in Wei.

• v: QUANTITY - ECDSA recovery id

• r: QUANTITY - ECDSA signature r

• s: QUANTITY - ECDSA signature s

Creates a filter in the node, to notify when a new block arrives. To check if the state has changed, call .

This method will use 20 .

Reference:

Parameters

None

Returns

QUANTITY - A filter id.

Creates a filter in the node, to notify when new pending transactions arrive. To check if the state has changed, call .

This method will use 20 .

Reference:

Parameters

None

Returns

QUANTITY - A filter id.

Returns the number of uncles in a block from a block matching the given block hash.

This method will use 20 .

Reference:

Parameters

1. QUANTITY|TAG - integer of a block number, or the string "latest", "earliest" or "pending", see the

Returns

QUANTITY - integer of the number of uncles in this block.

Returns the number of transactions sent from an address.

This method will use 30 .

Reference:

Parameters

1. DATA, 20 Bytes - address.

2. QUANTITY|TAG - integer block number, or the string "latest", "earliest" or "pending", see the

Returns

QUANTITY - String hex value representing integer of the number of transactions sent from this address.

Creates a filter object, based on filter options, to notify when the state changes (logs). To check if the state has changed, call .

This method will use 20 .

Reference:

A note on specifying topic filters: Topics are order-dependent. A transaction with a log with topics [A, B] will be matched by the following topic filters:

• [] "anything"

• [A] "A in first position (and anything after)"

• [null, B] "anything in first position AND B in second position (and anything after)"

• [A, B] "A in first position AND B in second position (and anything after)"

• [[A, B], [A, B]] "(A OR B) in first position AND (A OR B) in second position (and anything after)"

Parameters

Object - The filter options:

• fromBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block, "safe" for the latest safe block, "finalized" for the latest finalized block, or "pending", "earliest" for not yet mined transactions.

• toBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block, "safe" for the latest safe block, "finalized" for the latest finalized block, or "pending", "earliest" for not yet mined transactions.

• address: DATA|Array, 20 Bytes - (optional) Contract address or a list of addresses from which logs should originate.

• topics: Array of DATA, - (optional) Array of 32 Bytes DATA topics. Topics are order-dependent. Each topic can also be an array of DATA with "or" options.

Returns

QUANTITY - A filter id.

Returns the balance of the account of given address.

This method will use 20 .

Reference:

Parameters

1. DATA, 20 Bytes - address of the storage.

2. QUANTITY - integer of the position in the storage.

3. QUANTITY|TAG - integer block number, or the string "latest", "earliest" or "pending", see the

Returns

String - Hex value representing data at this storage position.

Returns information about a uncle of a block by number and uncle index position.

This method will use 20 .

Reference:

Parameters

1. QUANTITY|TAG - a block number, or the string "earliest", "latest" or "pending", as in the .

2. QUANTITY - the uncle's index position.

Returns

See

Returns the information about a transaction requested by transaction hash.

This method will use 20 .

Reference:

Parameters

1. DATA, 32 Bytes - hash of a transaction

Returns

Object - A transaction object, or null when no transaction was found:

• blockHash: DATA, 32 Bytes - hash of the block where this transaction was in. null when its pending.

• blockNumber: QUANTITY - block number where this transaction was in. null when its pending.

• from: DATA, 20 Bytes - address of the sender.

• gas: QUANTITY - gas provided by the sender.

• gasPrice: QUANTITY - gas price provided by the sender in Wei.

• hash: DATA, 32 Bytes - hash of the transaction.

• input: DATA - the data send along with the transaction.

• nonce: QUANTITY - the number of transactions made by the sender prior to this one.

• to: DATA, 20 Bytes - address of the receiver. null when its a contract creation transaction.

• transactionIndex: QUANTITY - integer of the transactions index position in the block. null when its pending.

• value: QUANTITY - value transferred in Wei.

• v: QUANTITY - ECDSA recovery id

• r: QUANTITY - ECDSA signature r

• s: QUANTITY - ECDSA signature s

Returns the number of uncles in a block from a block matching the given block hash.

This method will use 20 .

Reference:

Parameters

1. DATA, 32 Bytes - hash of a block

Returns

QUANTITY - integer of the number of uncles in this block.