The Explorer API provides Etherscan-compatible REST endpoints for querying on-chain data from the Fuse blockchain. Use it to retrieve account balances, transaction histories, token transfers, contract ABIs, event logs, block data, and network statistics. The API follows the module-and-action query pattern used by Blockscout’s JSON RPC v2 interface.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/fuseio/fuse-docs/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
Authentication
All requests require a public API key passed as a query parameter:Request pattern
Explorer API endpoints use query parameters to specify the module and action:Account module
Get native balance from a block
Must be
account.Must be
eth_get_balance.Your public API key.
The wallet address to query.
Block number as a string, or
latest, earliest, or pending. Defaults to latest.Response
JSON-RPC response ID.
JSON-RPC version string.
Balance in wei.
Example
Get native token balance
Must be
account.Must be
balance.Your public API key.
The wallet address to query.
Response
Response status (
1 for success).Response message (e.g.,
OK).Balance in wei as a string.
Example
Get balance for multiple addresses
Must be
account.Must be
balancemulti.Your public API key.
Comma-separated list of addresses. Maximum 20 addresses per request.
Response
Response status.
Response message.
Example
Get pending transactions for an address
Must be
account.Must be
pendingtxlist.Your public API key.
The wallet address to query.
Page number for pagination. Must be used together with
offset.Number of transactions per page. Must be used together with
page.Example
Get transactions by address
Must be
account.Must be
txlist.Your public API key.
The wallet address to query.
Block number to start search from.
Block number to stop search at.
Page number for pagination.
Number of transactions per page.
Sort order:
asc (ascending) or desc (descending). Default: desc.Response
Response status.
Response message.
Array of transaction objects.
Example
Available modules
The Explorer API exposes endpoints across the following modules. Each module is accessed using?module=<name> with the appropriate action parameter.
| Module | Description |
|---|---|
account | Account balances, transaction lists, and token transfer history |
block | Block information and block reward details |
contract | Contract ABI, source code, and verification status |
logs | Event log filtering and retrieval |
stats | Network statistics including total supply and validator counts |
token | Token information, supply, and holder lists |
transaction | Transaction receipt status and error details |