expand.network
Search
K

Blockchain

We support all major public blockchains
expand.network provides connectivity to various EVM and Non-EVM based chains for both, query(Read) and transaction(Write). So now, the developer does not need to worry about how different blockchains work. The developer will be required to know only the chainID to perform multiple operations on different chains.
For example, if a developer wants to send two transactions, one on the Ethereum mainnet and another on Solana, then they just need to call the sendtransaction API with different chain IDs in the request body.
Following are the common APIs implemented for all the various chains:-
Name
Type
Description
getbalance
Read
Get the balance or number of the given token in the requested public address.
getblock
Read
Get details of a block.
getgasprice
Read
Get the current gas price from the network.
getstorage
Read
Get data stored in the given slot.
gettransaction
Read
Get details of a transaction.
Read
Get the RPC of required chain.
getgasfees
Read
Retrieves gas fee spent in a particular range.
getusertransactions
Read
Get the historical transaction details for a specific user address. Available on Ethereum, Binance Smart Chain, Avalanche - P/C/X, Polygon, Fantom, and TON.
gethistoricalrewards
Read
Get the historical transaction details focusing on staking rewards for a specific user address. Available on Avax-P.
portfolio
Read
Get the comprehensive information about the assets/ tokens owned by a user. Available on Ethereum and Solana.
getflashbotblocks
Read
Get details of the flashbot blocks.
getflashbottransactions
Read
Get details of the flashbot transactions.
getflashbotbundle
Read
Get details of the specified flashbot bundle.
sendtransaction
Write
Sign and send transactions on the chain.
genericsmartcontractmethod
Write
Calls read functions of verified smart contracts. Available on ethereum.
decodetransaction
Write
Get the decoded transaction for the provided raw transaction. Available on ethereum, binance, avalanche, polygon, cronos, arbitrum, fantom, optimism, solana, and near.
Every chain requires a different set of parameters to perform the common operations. Please refer to the sub-sections for details.
To perform sendtransaction() successfully, the user needs to sign the transaction first.
For more details, click here.
If the user wants to pass the RPC manually, the user can either use their own RPC or use our provided RPC, by using /getpublicrpc endpoint.

/getpublicrpc

get
https://api.expand.network/chain/getpublicrpc
Get the RPC of required chain.
Sample Request
Sample Response
https://api.expand.network/chain/getpublicrpc?chainId=1000
{
"status": 200,
"msg": "success",
"data": {
"rpc": "https://api.trongrid.io"
}
}

Following is a sequence diagram for sendTransaction() process in chains:-

Sequence Diagram for sendTransaction