eth_getCode - zkSync
Example code for the eth_getCode JSON-RPC method. Сomplete guide on how to use eth_getCode JSON-RPC in GetBlock.io Web3 documentation.
Returns the contract bytecode deployed at a given address. An empty result (0x) indicates the address is an EOA, not a contract. Note: on zkSync, deployed bytecode is EraVM bytecode, not standard EVM bytecode — use zks_getBytecodeByHash for queries by hash.
Parameters
address
string
Yes
20-byte address of the contract
blockParameter
string
Yes
Block number in hex, or "latest", "earliest", "pending", "safe", "finalized"
Request Example
curl --location --request POST 'https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
"jsonrpc": "2.0",
"method": "eth_getCode",
"params": [
"0x36615cf349d7f6344891b1e7ca7c72883f5dc049",
"latest"
],
"id": "getblock.io"
}'import axios from 'axios';
const data = JSON.stringify({
"jsonrpc": "2.0",
"method": "eth_getCode",
"params": [
"0x36615cf349d7f6344891b1e7ca7c72883f5dc049",
"latest"
],
"id": "getblock.io"
});
const config = {
method: 'post',
url: 'https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/',
headers: {
'Content-Type': 'application/json'
},
data: data
};
axios(config)
.then(response => console.log(JSON.stringify(response.data, null, 2)))
.catch(error => console.log(error));Response Example
Response Parameters
result
string
Contract bytecode in hex (EraVM format), or 0x if the address is an EOA
Use Cases
Distinguishing contracts from EOAs
Verifying contract deployment
Detecting proxy contracts and their implementations
Error Handling
403
Forbidden
Missing or invalid <ACCESS-TOKEN>
-32602
Invalid params
Request parameters are missing or malformed
429
Too Many Requests
Rate limit exceeded for your plan
SDK Integration
Last updated
Was this helpful?