eth_createAccessListHTTP

Simulates a transaction to produce an EIP-2930 access list. Compare estimates with and without the list: its upfront cost can outweigh access savings.

Chain EthereumTransport HTTPTry-it live

How to use

Pick an API key (or paste one) in the Try it panel.
Object params use a tall JSON editor — click Fill example if available.
Send request — live against the gateway; counts toward daily quota.

Parameters

JSON-RPC positional arguments — order matches the array sent in params. Index badges below match array positions.

txOBJECTrequired

Transaction call object (from, to, input/data, value, gas and fee fields). Use the intended sender and an explicit gas ceiling for reproducible simulation. Balance checks, fee defaults and gas caps vary by client.

blockQUANTITY|TAGoptional

Block number or tag.

params array (shape)

eth_createAccessList · paramsjson

1[
2  {
3    "from": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
4    "to": "0xdAC17F958D2ee523a2206206994597C13D831ec7",
5    "data": "0x313ce567",
6    "gas": "0x186a0"
7  },
8  "latest"
9]

Try it

Live request via the gateway — counts toward your account's daily quota. Chain: ethereum

JSON mode

API key

Try-it runs with one of your own keys — sign in or create a free account first.

Parameters

0txOBJECTrequired

Paste a JSON object. Indent freely — we parse it into the params array.

1blockQUANTITY|TAGoptional

Block number or tag.

Example request

eth_createAccessList · requestbash

1curl 'https://ethras.org/v1/ethereum/<YOUR_KEY>' \
2  -H 'Content-Type: application/json' \
3  -d '{
4    "id": 1,
5    "jsonrpc": "2.0",
6    "method": "eth_createAccessList",
7    "params": [
8      {
9        "from": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
10        "to": "0xdAC17F958D2ee523a2206206994597C13D831ec7",
11        "data": "0x313ce567",
12        "gas": "0x186a0"
13      },
14      "latest"
15    ]
16  }'

Example response

Illustrative example: long hex values and object fields may be shortened for readability. Available fields depend on the network, client, protocol upgrade and transaction type.

eth_createAccessList · responsejson

1{
2  "jsonrpc": "2.0",
3  "id": 1,
4  "result": {
5    "accessList": [
6      {
7        "address": "0xdac17f958d2ee523a2206206994597c13d831ec7",
8        "storageKeys": ["0x0000000000000000000000000000000000000000000000000000000000000009"]
9      }
10    ],
11    "gasUsed": "0x64f8"
12  }
13}

Response fields

The result row describes the complete result; other rows describe its object fields or array elements. Indented rows describe nested members. For subscriptions,params.* rows describe later notifications rather than the initial reply.

Field	Type	Description
`accessList`	`ARRAY`	Addresses and storage slots the transaction would access.
└`address`	`DATA(20B)`	Account to pre-warm; it need not be a contract or have storage keys.
└`storageKeys`	`DATA(32B)[]`	Storage slots accessed under this address.
`gasUsed`	`QUANTITY`	Estimated gas for the simulated transaction with the generated access list, not a promise of lower gas use.
`error`	`STRING`	Optional execution error inside the result. Request-validation failures may instead be top-level JSON-RPC errors.