Bitcoin RPC Endpoints

The endpoint exposes the Bitcoin Core JSON-RPC interface. Blockchain calls such as getblockchaininfo, getblock, getblockhash, and gettxout read chain state. Raw transaction calls such as getrawtransaction, decoderawtransaction, and sendrawtransaction handle transactions. Utility calls such as estimatesmartfee and validateaddress round out the set. Wallet, mining, and control RPCs are not available on shared endpoints.

Yes. Dwellir runs unpruned Bitcoin Core nodes with txindex enabled. getrawtransaction returns any confirmed transaction by txid without a block hash hint, all the way back to the 2009 genesis block.

No. Bitcoin Core speaks HTTP JSON-RPC only, so the endpoint has no WebSocket URL. Poll getbestblockhash or getblockcount to detect new blocks. With a 10-minute average block time, polling once every 30 to 60 seconds is enough for most applications.

Sign the transaction locally, then call sendrawtransaction with the hex-encoded transaction. The node validates it, adds it to its mempool, and relays it to peers. Call getmempoolentry with the txid to confirm the node accepted it, and gettransaction is not needed because the endpoint has no wallet.

The shared endpoint covers wallets, explorers, and payment backends. Move to a dedicated cluster when you index the full chain from block 0, watch the mempool at high request rates, or need custom node settings such as a larger mempool, ZMQ notifications, or extra indexes. Dedicated clusters run in the same Stockholm data centers as the shared fleet.