Block Explorer Node
The Block Explorer node reads on-chain data directly from public block explorers. One node covers six query types — address balance, transaction details, token transfers, contract info, gas prices, and block info — across the EVM chains (Ethereum, BSC, Polygon, Arbitrum) via the Etherscan family, plus Bitcoin via Blockchain.com. Pick an explorer, a network, and a query type, and the input fields change to match. The output shape is discriminated on the query type, so downstream nodes always know what they're reading.
Configuration
General
Give this node a custom name to identify it in your workflow
Continue workflow if this node fails
API Credential
One Etherscan key covers all EVM explorers (not used for Bitcoin)
NickAI credits or your own Etherscan API key
Query
Choose the explorer, network, and what to fetch
Required for address balance and token transfers. Supports the f(x) toggle.
Why Block Explorer
Block explorers index everything that happens on a chain — every balance, transaction, contract, and block — and expose it over a free REST API. The Block Explorer node brings that into your workflows without running a node or wrangling RPC:
- Wallet monitoring — track a wallet's native balance and react when it moves.
- Transaction tracking — confirm a tx landed, check its status, and read its details.
- Contract verification — fetch a contract's verified source, ABI, and proxy implementation.
- Gas optimization — read the live gas oracle and act only when fees are low.
- Multichain on one key — the four EVM explorers share a single Etherscan key (V2 multichain API), selected by chain.
Explorers & Networks
| Explorer | Chain | Native | Testnet | Query types |
|---|---|---|---|---|
| Etherscan | Ethereum | ETH | Sepolia | All six |
| BscScan | BSC | BNB | BSC Testnet | All six |
| PolygonScan | Polygon | POL | Amoy | All six |
| Arbiscan | Arbitrum | ETH | Arbitrum Sepolia | All six |
| Blockchain.com | Bitcoin | BTC | — | Balance, Transaction, Block info |
Query Types
| Query type | Required field | Returns |
|---|---|---|
| Address balance | address | Native balance (raw base units + human-readable) |
| Transaction | txHash | Hash, from/to, value, block, and status |
| Token transfers | address (optional token filter) | Recent ERC-20 transfers (EVM only) |
| Contract info | contractAddress | Name, verification status, ABI, source, proxy impl. (EVM only) |
| Gas prices | — | Safe / propose / fast / base fee in gwei (EVM only) |
| Block info | blockNumber | Number, hash, timestamp, tx count, miner, gas used/limit |
Configuration
| Field | Description |
|---|---|
| API Credential | NickAI Credits (default) or your own Etherscan key. One key covers all EVM explorers. Bitcoin needs no key. See Billing. |
| Explorer | Which explorer to query. EVM: Etherscan / BscScan / PolygonScan / Arbiscan. Bitcoin: Blockchain.com. |
| Network | Mainnet or testnet. EVM testnets map to Sepolia / BSC Testnet / Amoy / Arbitrum Sepolia. |
| Query Type | What to fetch. The list is filtered to what the selected explorer supports. |
| Address | Wallet or contract address. Required for address balance and token transfers. Supports the f(x) toggle. |
| Transaction Hash | The tx hash/id. Required for transaction mode. Supports f(x). |
| Contract Address | Required for contract info (EVM only). Supports f(x). |
| Block Number | A block number or latest (EVM) / a height or hash (Bitcoin). Required for block info. Supports f(x). |
| Token Contract | Optional ERC-20 filter for token transfers. Leave empty for all tokens. |
| Result Limit | Max rows for token transfers (1–100). Default: 25. |
Dynamic Fields
The address, transaction hash, contract address, and block number fields support the f(x) toggle. Click it to switch a field from a static value to an expression that resolves at runtime from an upstream node:
{function.walletAddress}
This lets you build workflows where the address or txid comes from an earlier node — for example, looping over a list of wallets, or checking a transaction whose hash was produced by an Exchange Order node.
Setting Up Your API Key
EVM queries run on NickAI credits by default. To run them free on your own key (and avoid sharing rate limits), connect an Etherscan API key. Bitcoin needs no key.
Step 1: Get an Etherscan API Key
- Sign up at etherscan.io/register ↗ (free) and verify your email.
- Go to etherscan.io/apidashboard ↗ → + Add.
- Name the key and copy it.
The free tier allows 5 calls/sec and 100,000 calls/day — and the same key works across BSC, Polygon, and Arbitrum via the V2 multichain API.
Step 2: Add the Credential in NickAI
- Go to Credentials in NickAI.
- Click Add Credential and select Etherscan API.
- Paste your API key, name it (e.g. "My Etherscan Key"), and save.
Step 3: Select in the Node
- Open your workflow and select the Block Explorer node.
- In the API Credential section, select your credential. Running with your own key is free.
Billing & Credits
The node runs one of two ways, chosen by the API Credential field:
- NickAI Credits (default) — runs on NickAI's Etherscan access and charges 2 NickAI credits per call.
- Your own Etherscan key — runs on your key; NickAI charges nothing for the node step.
2 on the NickAI path, 0 with your own key. Bitcoin queries are keyless and always run on the NickAI path.Workflow Examples
Wallet Balance Monitor
Alert when a wallet's balance drops below a threshold.
The Block Explorer fetches the native balance, the Conditional checks {wallet.balance.formatted} against a threshold, and Telegram fires only when it's low.
Gas Price Optimizer
Run an action only when gas is cheap.
The Conditional gates on {gas.gas.fast} so the downstream action only runs when network fees are favorable.
Transaction Confirmation Watcher
Confirm a transaction landed, then notify.
Pipe a tx hash in via the f(x) toggle (e.g. from an Exchange Order node), check {tx.transaction.status}, and email on success.
Output
Every result includes the queryType discriminator and a metadata block; the data lives under a key that matches the query type.
| Path | Description |
|---|---|
| {block_explorer.queryType} | Which query ran (address_balance, transaction, token_transfers, contract_info, gas_prices, block_info) |
| {block_explorer.metadata.source} | Explorer display name (e.g. Etherscan) |
| {block_explorer.metadata.explorer} | Explorer id (e.g. etherscan) |
| {block_explorer.metadata.network} | mainnet or testnet |
| {block_explorer.metadata.requestedAt} | ISO timestamp |
| {block_explorer.metadata.creditsUsed} | NickAI credits charged (2, or 0 with your own key) |
Output by query type
| Query type | Key | Fields |
|---|---|---|
| Address balance | {…balance} | address, raw, formatted, symbol, decimals |
| Transaction | {…transaction} | hash, from, to, value, blockNumber, status, raw |
| Token transfers | {…transfers[]}, {…total} | per row: hash, from, to, value, tokenName, tokenSymbol, tokenDecimals, contractAddress, blockNumber, timeStamp |
| Contract info | {…contract} | contractName, isVerified, compilerVersion, abi, sourceCode, implementation |
| Gas prices | {…gas} | safe, propose, fast, baseFee, unit |
| Block info | {…block} | number, hash, timestamp, transactionCount, miner, gasUsed, gasLimit, raw |
block_explorer with your node's edge label. If the edge to the next node is labeled wallet, use {wallet.balance.formatted}.raw, in wei/satoshis) and human-readable (formatted). Token-transfer value is left in base units — divide by 10 ^ tokenDecimals to get the human amount.Example Output
{
"queryType": "address_balance",
"balance": {
"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
"raw": "5690864439481747771",
"formatted": "5.690864439481747771",
"symbol": "ETH",
"decimals": 18
},
"metadata": {
"source": "Etherscan",
"explorer": "etherscan",
"network": "mainnet",
"requestedAt": "2026-06-24T22:58:56.844Z",
"creditsUsed": 0
}
}
Common Errors
| Error | Cause | Fix |
|---|---|---|
| NickAI block explorer service is not configured | No platform Etherscan key on the NickAI path | Connect your own Etherscan API key |
| Block explorer credential not found | Selected credential was deleted | Re-select or re-create the Etherscan credential |
| Transaction not found | Wrong hash, wrong chain, or not yet indexed | Verify the hash and that the explorer/network matches the chain |
| Blockchain.com (Bitcoin) supports mainnet only | Testnet selected for Bitcoin | Switch the network to mainnet |
| Blockchain.com does not support the "…" query | Token transfers / contract info / gas prices on Bitcoin | Use a supported query (balance, transaction, block info) or switch to an EVM explorer |
| Etherscan API error | Rate limit, bad key, or transient outage | Check your key/limits; retry — the node times out after 15s |
Next Steps
- Conditional Node — Route on balances, gas prices, or transaction status.
- LLM Node — Summarize contract source or transaction activity with AI.
- Function Node — Parse token transfers or format raw values with custom code.
- Loop Node — Iterate over a list of wallets or transactions.
- Telegram Notification — Deliver on-chain alerts.
- Credentials — Connect your Etherscan API key.