Also added field is_double_spend to the response of the get_confidence API call. December 11, Added Network Confidence rating for unconfirmed transactions. September 14, Bugfix in get_address_balance. Now correctly returns balance for given number of confirmations. Go to the API. July 18, Added realtime balance updates to. getbalance¶. getbalance ("dummy" minconf include_watchonly). Returns the total available balance. The available balance is what the wallet considers currently spendable, and is thus affected by options which limit spendability such as -spendzeroconfchange. Get Bitcoin address balance api - Experts uncover unbelievable effects - SoChain Bitcoin list - Bitcoin. your entire Bitcoin, Litecoin, be used to receive this could help by - SoChain BitGo API know the balance of (REST and Realtime) - I have created a wallet balance (with account for a command.
Api get bitcoin address balancebitcoind - How to get a bitcoin address's balance? - Bitcoin Stack Exchange
ECPair bigi. Buffer tosign , " hex ". Sign keychain. SendMicro micro if err! GetTXConf "bb01beeabe16b5d59dd3edf41abbeeffffdd2a" if err! CreatePayFwd gobcy. ListPayFwds if err! DeletePayFwd "6fbe2bfeacdcbc4d5fcc " if err! CreateHook gobcy. ListHooks if err! GetHook "86acb-babdead4" if err! DeleteHook "86acb-babdead4" if err!
A rolling average of the fee in satoshis paid per kilobyte for transactions to be confirmed within 1 to 2 blocks. A rolling average of the fee in satoshis paid per kilobyte for transactions to be confirmed within 3 to 6 blocks.
A rolling average of the fee in satoshis paid per kilobyte for transactions to be confirmed in 7 or more blocks. Optional The current height of the latest fork to the blockchain; when no competing blockchain fork present, not returned with endpoints that return Blockchains. Optional The hash of the latest confirmed block in the latest fork of the blockchain; when no competing blockchain fork present, not returned with endpoints that return Blockchains.
The height of the block in the blockchain; i. The depth of the block in the blockchain; i. Optional Raw size of block including header and all transactions in bytes. Not returned for bitcoin blocks earlier than height The time BlockCypher's servers receive the block. Our servers' clock is continuously adjusted and accurate. The number used by a miner to generate this block. To get more details about specific transactions, you must concatenate this URL with the desired transaction hash es.
The Merkle root of this block. Optional If there are more transactions that couldn't fit in the txids array, this is the BlockCypher URL to query the next set of transactions within a Block object. Height of the block that contains this transaction. If this is an unconfirmed transaction, it will equal The hash of the transaction.
While reasonably unique, using hashes as identifiers may be unsafe. The likelihood that this transaction will make it to the next block; reflects the preference level miners have to include this transaction.
Can be high, medium or low. Version number, typically 1 for Bitcoin transactions. Time when transaction can be valid. Can be interpreted in two ways: if less than million, refers to block height. If more, refers to Unix epoch time. Number of subsequent blocks, including the block the transaction is in.
Unconfirmed transactions have 0 confirmations. Optional The percentage chance this transaction will not be double-spent against, if unconfirmed.
For more information, check the section on Confidence Factor. Optional Time at which transaction was included in a block; only present for confirmed transactions. Optional Number of peers that have sent this transaction to BlockCypher; only present for unconfirmed transactions.
Optional Address BlockCypher will use to send back your change, if you constructed this transaction. If not set, defaults to the address from which the coins were originally sent. Optional Hash of the block that contains this transaction; only present for confirmed transactions. Optional Canonical, zero-indexed location of this transaction in a block; only present for confirmed transactions. Optional If this transaction is a double-spend i.
Data protocols currently detected: blockchainid ; openassets ; factom ; colu ; coinspark ; omni. Optional Hex-encoded bytes of the transaction, as sent over the network.
The previous transaction hash where this input was an output. Not present for coinbase transactions. The index of the output being spent within the previous transaction.
The value of the output being spent within the previous transaction. Legacy 4-byte sequence number , not usually relevant unless dealing with locktime encumbrances. Optional Number of confirmations of the previous transaction for which this input was an output. Currently, only returned in unconfirmed transactions.
Only used when constructing transactions via the Creating Transactions process. Addresses that correspond to this output; typically this will only have a single address, and you can think of this output as having "sent" value to the address contained herein.
Optional The transaction hash that spent this output. Only returned for outputs that have been spent. The spending transaction may be unconfirmed. The age of the transaction in milliseconds, based on the earliest time BlockCypher saw it relayed in the network. Number of peers that have sent this transaction to BlockCypher; only positive for unconfirmed transactions. A number from 0 to 1 representing BlockCypher's confidence that the transaction won't be double-spent against.
If it's unconfirmed, this will equal The likelihood that the enclosing transaction will make it to the next block; reflects the preference level miners have to include the enclosing transaction. If it's an input, or an unspent output, it will be false. Optional The past balance of the parent address the moment this transaction was confirmed.
Not present for unconfirmed transactions. Optional Time this transaction was received by BlockCypher's servers; only present for unconfirmed transactions. Array of signatures corresponding to all the data in tosign , typically provided by you. Array of public keys corresponding to each signature. In general, these are provided by you, and correspond to the signatures you provide.
Optional Array of hex-encoded, work-in-progress transactions; optionally returned to validate the tosign data locally. Optional Array of errors in the form "error":"description-of-error".
This is only returned if there was an error in any stage of transaction generation, and is usually accompanied by a HTTP code. Optional The encoding of your data, can be either string for plaintext or hex for hex-encoded. If not set, defaults to hex. Optional The hash of the transaction containing your data; only part of return object.
Optional Address BlockCypher will use to send back your change. While not required, we recommend that you set a change address. The guarantee usually takes around 8 seconds. If manually set to false , the Microtransaction endpoint will return as soon as the transaction is broadcast. Optional Hex-encoded data for you to sign after initiating the microtransaction. Optional Hex-encoded signatures for you to send back after having received and signed tosign.
Optional Partial list of inputs that will be used with this transaction. Inputs themsleves are heavily pared down, see cURL sample.
Optional Partial list of outputs that will be used with this transaction. Outputs themselves are heavily pared down, see cURL sample. BlockCypher pays these fees for the first 8, microtransactions, but like regular transactions, it is deducted from the source address thereafter. Optional The requested address. Optional The requested wallet object.
Only returned if querying by wallet name instead of public address. Optional The requested HD wallet object. Only returned if querying by HD wallet name instead of public address. Balance of confirmed satoshis on this address. This is the difference between outputs and inputs on this address, but only for transactions that have been included into a block i. Balance of unconfirmed satoshis on this address.
Can be negative if unconfirmed transactions are just spending outputs. Only unconfirmed transactions haven't made it into a block are included. Number of confirmed transactions on this address. Number of unconfirmed transactions for this address. Final number of transactions, including confirmed and unconfirmed transactions, for this address.
Optional To retrieve base URL transactions. Optional Array of full transaction details associated with this address. Usually only returned from the Address Full Endpoint. Optional Array of transaction inputs and outputs for this address. Usually only returned from the standard Address Endpoint. Optional All unconfirmed transaction inputs and outputs for this address.
Optional If true , then the Address object contains more transactions than shown. Useful for determining whether to poll the API for more transaction information. Wallet import format , a common encoding for the private key. Optional Array of public keys to provide to generate a multisig address. Optional If generating a multisig address, the type of multisig script; typically "multisig-n-of-m", where n and m are integers. Optional If generating an OAP address , this represents the parent blockchain's underlying address the typical address listed above.
A single chain is returned if the wallet has no subchains. The extended public key all addresses in the HD wallet are derived from. It's encoded in BIP32 format. Optional Hex-encoded metadata that can optionally be encoded into the issue or transfer transaction.
Unique indentifier associated with this asset; can be used to query other transactions associated with this asset. This transaction's unique hash; same as the underlying transaction on the asset's parent blockchain. Optional Time this transaction was confirmed; only returned for confirmed transactions. Optional Associated hex-encoded metadata with this transaction, if it exists. Array of input data, which can be seen explicitly in the cURL example.
Very similar to array of TXInput s, but with values related to assets instead of satoshis. Array of output data, which can be seen explicitly in the cURL example.
Very similar to array of TXOutput s, but with values related to assets instead of satoshis. Type of event; can be unconfirmed-tx , new-block , confirmed-tx , tx-confirmation , double-spend-tx , tx-confidence. The hash can either be for a block or a transaction. If used, requires a user token. A wallet name can also be used instead of an address, which will then match on any address in the wallet.
You'll receive an updated TX for every confirmation up to this amount. The maximum allowed is 10; if not set, it will default to 6.
You'll receive a TX once this threshold is met. Will accept any float between 0 and 1, exclusive; if not set, defaults to 0. The address which will automatically forward to destination ; generated when a new request is created. Optional Address to forward processing fees, if specified. Allows you to receive a fee for your own services. Optional Fixed processing fee amount to be sent to the fee address. Optional Percentage of the transaction to be sent to the fee address. Automatically sets up a WebHook.
Optional Mining fee amount to include in the forwarding transaction, in satoshis. If not set, defaults to 10, Optional History of forwarding transaction hashes for this payment forward; not present if this request has yet to forward any transactions. IP address and port, of the form "0. Optional URL to get the next page of results; only present if there are more results to show. Results of analytics job; structure of results are dependent on engine -type of query, but are generally either strings of address hashes or JSON objects.
Filters response to only include transaction hashes after txstart in the block. Filters response to only include a maximum of limit transactions hashes in the block.
Maximum value allowed is If omitWalletAddresses is true and you're querying a Wallet or HDWallet , the response will omit address information useful to speed up the API call for larger wallets. If includeScript is true , includes raw script of input or output within returned TXRefs. If true , includes the confidence attribute useful for unconfirmed transactions within returned TXRefs. For more info about this figure, check the Confidence Factor documentation.
Filters response to only include transactions below before height in the blockchain. Filters response to only include transactions above after height in the blockchain. This ensures paging by block height never misses TXRefs. Defaults to , maximum is If set, only returns the balance and TXRefs that have at least this number of confirmations. Filters response to only include TXRefs above confidence in percent; e. For more detail on confidence, check the Confidence Factor documentation.
This ensures paging by block height never misses TXs. Defaults to 10, maximum is If set, only returns the balance and TXs that have at least this number of confirmations. Filters response to only include TXs above confidence in percent; e. Litecoin Only. Replaces P2SH prefix with legacy 3 instead of M. Disabled by default. If true , includes the confidence attribute useful for unconfirmed transactions within returned TXs.
If omitWalletAddresses is true , the response will omit address information useful to speed up the API call for larger wallets. Returns only used addresses if set to true and only unused if false. Only valid on HD wallets. Returns only addresses with zero balance if set to true and only addresses with non-zero balance if false.
Derives address es on this specific subchain. If not set, address will be generated on the first chain in the HD wallet. Default to true. If set to false will not try to check the balance of the subsequent addresses.
Set to false if this endpoint is too slow. If true , includes the confidence attribute useful for unconfirmed transactions. Just from the bitcoin-qt client? Or any other lib for cpp? Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. The Overflow Talking crypto. Podcast What can you program in just one tweet? Featured on Meta. New Feature: Table Support.
Swag is coming back! Linked 0. Related 2. It is not necessary to use web wallets to create addresses. So if you are running a bitcoin daemon locally you can just query them. The documentation for the same is located at. So just go to the official website of bitcoin and find all of the methods. Learn more. How to check Bitcoin address balance from my application?
Ask Question. Asked 7 years ago. Active today. Viewed 10k times. If you don't want to use an API, download the bitcoin client, fetch the blockchain and parse it. Active Oldest Votes. LF00 LF00 Abishek Abishek 9, 17 17 gold badges 64 64 silver badges bronze badges. The thing is I want to know the balance of an address that is not mine, so your solution doesn't apply.