API / RPC Reference

Mobick mainnet data can be queried via the public explorer's REST API. It requires no authentication, and responses are in JSON.

Endpoint Hosts

Below are the main endpoints for the mempool instance (blockchain.mobick.info). Because it is Bitcoin-based, it is compatible with the esplora API specification.

Blocks

GET /api/blocks/tip/height      # Current block height
GET /api/blocks/tip/hash        # Latest block hash
GET /api/blocks                 # List of recent blocks (newest first)
GET /api/block/:hash            # Details of a specific block
GET /api/block-height/:height   # Height → block hash

Example

curl https://blockchain.mobick.info/api/blocks/tip/height
# 47514

Address (Balance & Transactions)

GET /api/address/:address       # Address summary (funded/spent/tx_count)
GET /api/address/:address/txs   # Transaction list for the address

Balance calculation: chain_stats.funded_txo_sum − chain_stats.spent_txo_sum (unit: sat, ÷100,000,000 = BMB)

curl https://blockchain.mobick.info/api/address/bc1qyt8cfzhz2dmnglhu5uklm2fvfftg0kga3hl3hp
# { "chain_stats": { "funded_txo_sum": 100000000000000, "spent_txo_sum": 0, ... } }
# → 1,000,000 BMB

The public goods panel on the homepage uses exactly this endpoint to sum the balances of the 16 wallets in real time.

Transactions

GET /api/tx/:txid               # Transaction details
GET /api/tx/:txid/status        # Confirmation status

Mempool & Network Statistics

GET /api/mempool                     # Pending transaction summary
GET /api/mempool/recent              # Recently received transactions
GET /api/v1/statistics/24h           # 24-hour mempool statistics
GET /api/v1/difficulty-adjustment    # Difficulty adjustment info
GET /api/v1/mining/hashrate/3d       # Hashrate
GET /api/v1/fees/recommended         # Recommended fees

WebSocket (Real-time)

wss://blockchain.mobick.info/api/v1/ws

Send {"action":"want","data":["blocks","mempool-blocks"]} to subscribe to new block and mempool updates.

CORS Notes

When calling directly from a browser, you may run into CORS restrictions. For frontends, we recommend proxying through a server (e.g., a Next.js Route Handler).

Coming soon: JSON-RPC (Bitcoin Core-style) port and authentication details for connecting directly to a node are covered in the Running a Node document.