What is it?
The INTcoin block explorer at https://explorer.international-coin.org is a public web view of the canonical mainnet chain — every block, every transaction, every address, with no account or login required. It runs against the EU server’s full node and stays in sync with the network in real time.
Quick links
- Home / latest blocks: https://explorer.international-coin.org
- Rich list (top addresses by balance): https://explorer.international-coin.org/explorer/richlist.html
- Search any block / transaction / address: search bar at the top of every page
- REST API root:
/api/v1/— every panel you see in the UI is also available as JSON if you’re integrating
Common things you can do
Look up a transaction
Paste a transaction ID (txid) into the search bar. You’ll see:
- Block + height the tx was confirmed in (or “unconfirmed” if still in mempool)
- Inputs — UTXOs being spent, with amounts and source addresses
- Outputs — destination addresses + amounts (plus
OP_RETURNif any) - Confirmations — how many blocks have built on top since
- Raw hex — the serialised transaction; useful for debugging or rebroadcasting
Look up an address
Paste an INT bech32 address (int1q...) into the search bar. You’ll see:
- Current balance (sum of unspent outputs)
- Total received / sent lifetime totals
- Transaction history — every tx this address appears in, newest first
- First seen + last activity timestamps
Note: the explorer only indexes the canonical chain. If your node is on a local fork (which can happen during heavy reorgs or if you’re running standalone P2P miner without a synced full node), the explorer won’t show your fork’s data — that’s expected.
Look up a block
Paste either a block hash or a block height (e.g. 8615). You’ll see:
- Header fields —
nBits, timestamp, merkle root, previous block hash, difficulty - Transactions — full list, with the coinbase highlighted
- Miner address — coinbase output recipient
- Block reward — coinbase value (subsidy + fees)
- Size + weight — bytes + weight units
Watch the chain advance live
The home page auto-refreshes new blocks via WebSocket. If you’re waiting for a transaction to confirm, leaving the home page open is the simplest “is the chain advancing” check.
REST API for integration
Every panel in the UI also has a JSON endpoint. A few examples:
GET /api/v1/block/<height-or-hash> # full block including all txs
GET /api/v1/tx/<txid> # transaction detail
GET /api/v1/address/<address> # address summary + history
GET /api/v1/blocks/recent # last N blocks
GET /api/v1/mempool # current mempool snapshot
GET /api/v1/stats # chain height, hashrate, peer count
Responses are standard JSON. Rate limits apply but are generous for normal use; if you’re polling at high frequency for an exchange or service integration, contact the team via #development on Discord so we can coordinate.
Privacy note
Like every blockchain explorer, this is a public view. Anything you look up — addresses, transactions, blocks — is visible to your network path (Tor / I2P / clearnet) and to the explorer’s logs. If you want to inspect your own wallet’s state without anyone seeing the address, run intcoin-cli getaddressinfo <addr> against your local full node instead.
When the explorer disagrees with your wallet
If your wallet shows a balance the explorer doesn’t (or vice versa), it usually means one of three things:
- Your node is on a different chain. Run
intcoin-cli getbestblockhashand compare against the explorer’s tip hash on the home page. If they differ, your node is on a fork — fix by re-syncing or by following the steps in Common issues. - The transaction is unconfirmed. Wallet sees pending txs the explorer’s address page won’t include in the confirmed total until they land in a block.
- Address-index is out of sync. Rare, but if the EU node ever reindexes (
-reindex), the explorer can briefly return 503 on address endpoints until it catches up.
For anything that looks wrong, post the txid / address / block hash in the #issues Discord channel or in Help & Support and we’ll dig.
— INT-devs