Sei Explorer

Fetch blockchain data from Sei network

Overview

This node, named "Sei Explorer," allows users to fetch various types of blockchain data from the Sei network using Ethereum-compatible JSON-RPC calls. It supports querying block information, transaction details, account balances, and calling read-only smart contract methods on the Sei EVM chains.

Common scenarios where this node is beneficial include:

Monitoring blockchain state by retrieving specific block or transaction data.
Checking SEI token balances for given accounts.
Interacting with deployed smart contracts to read data without sending transactions.
Integrating Sei blockchain data into workflows for analytics, notifications, or automation.

Practical examples:

Fetching the latest block info to track new blocks.
Getting detailed status and logs of a particular transaction hash.
Querying an account's SEI balance before performing further operations.
Calling a contract method like balanceOf or totalSupply to display token stats.

Properties

Name	Meaning
Blockchain	Target Sei EVM network. Options: • Sei Mainnet EVM (Pacific-1) • Sei Testnet EVM (Atlantic-2) • Custom (requires custom RPC URL)
Custom RPC	Custom Sei EVM RPC endpoint URL. Required if "Custom" blockchain option is selected.
Query Type	Type of query to perform. Options: • Get Block Info — Retrieve information about a specific block. • Get Transaction Details — Retrieve details of a specific transaction. • Get Account Balance — Get SEI balance of an account. • Call Contract Method — Call a read-only contract method.
Block Number	Block number to query (use `"latest"` for the latest block). Used only when Query Type is "Get Block Info".
Transaction Hash	Transaction hash to query. Used only when Query Type is "Get Transaction Details".
Account Address	Account address to query balance for. Used only when Query Type is "Get Account Balance".
Contract Address	Smart contract address. Used only when Query Type is "Call Contract Method".
Contract ABI	Contract ABI (Application Binary Interface) in JSON format for decoding and encoding contract method calls. Used only when Query Type is "Call Contract Method".
Method Name	Contract method name to call. Used only when Query Type is "Call Contract Method".
Method Arguments	List of arguments to pass to the contract method call. Each argument is a string value. Used only when Query Type is "Call Contract Method".

Output

The node outputs an array with one item per input item. Each output item contains a json object with the following structure:

queryType: The type of query performed (e.g., blockInfo, transactionDetails, accountBalance, contractCall).
result: The result of the query, varying by query type:
- For Get Block Info: An object representing the block data including transactions.
- For Get Transaction Details: An object containing transaction and receipt details.
- For Get Account Balance: An object with address, raw balance (in Wei), and balanceInEth (converted to Ether units).
- For Call Contract Method: An object with contractAddress, methodName, arguments passed, rawResult (hex data), and decodedResult (decoded return values).
rpcUrl: The RPC endpoint used for the query.
chainId: The identifier of the blockchain network queried.
timestamp: ISO timestamp of when the query was executed.

If an error occurs during the query, the output includes:

error: true
errorMessage: Description of the error encountered.
Other metadata fields as above.

The node does not output binary data.

Dependencies

Requires access to a Sei EVM-compatible JSON-RPC endpoint. Users can select default public RPC URLs for mainnet or testnet or provide a custom RPC URL.
Uses the ethers library internally for encoding/decoding contract calls.
No credentials are required unless a private/custom RPC endpoint demands authentication (not handled explicitly by this node).

Troubleshooting

Missing Custom RPC URL: If "Custom" blockchain is selected but no RPC URL is provided, the node throws an error indicating that a custom RPC URL is required.
Unknown Network: Selecting a blockchain network not recognized by the node results in an error.
Invalid Query Type: Providing an unsupported query type causes an error.
RPC Errors: If the RPC endpoint returns an error response, the node surfaces the error message prefixed with "RPC Error:".
Contract Call Failures: Errors in encoding or decoding contract method calls may occur if the ABI or method name is incorrect or arguments do not match the contract signature.
Empty or Invalid Inputs: Missing required parameters for the selected query type (e.g., missing transaction hash for transaction details) will cause errors.

To resolve these issues:

Ensure all required parameters for the chosen query type are correctly set.
Use valid RPC endpoints with proper connectivity.
Verify contract ABI and method names carefully.
Check network selection matches the intended chain.