GET parameters: "address".Returns main stored informations about the provided address: total received and spent coins, both confirmed and unconfirmed.
GET parameters: "address", "page" (optional, default is 1).Returns up to 10 stored transactions regarding the provided address. Offset can be moved by setting the "page" parameter.
GET parameters: "hash" or "index".Directly returns the client's answer by calling the "getblock" function, if providing an index it calls "getblockhash" before. It is recommended to use either getBlockByHash or getBlockByIndex for slightly better performance.
GET parameters: "hash".Just like calling getBlock with a "hash" parameter, but avoids futile checks for an eventual "index" parameter, being slightly faster.
GET parameters: "index".Just like calling getBlock with a "index" parameter, but avoids futile checks for an eventual "hash" parameter, being slightly faster.
No parameters.Directly returns the client's answer by calling the "getblockchaininfo" function.
GET parameters: "index".Directly returns the client's answer by calling the "getblockhash" function.
GET parameters: "page" (optional, default is 1).Returns up to 10 blocks directly from the client. Offset can be moved by setting the "page" parameter.
GET parameters: "page" (optional, default is 1).Returns up to 10 stored transactions. Offset can be moved by setting the "page" parameter.
No parameters.Directly returns the client's answer by calling the "getblockchaininfo" function.
GET parameters: "id".Directly returns the client's answer by calling the "getrawtransaction" function.
No parameters.Returns the stored total coin supply.
GET parameters: "id" (either transaction's literal id or numeric index).Returns main stored informations about the provided transaction.
GET parameters: "string" (must be a block index, block hash, transaction hash or address).Returns a local URL to a page showing informations about the block, transaction or address provided..