A visualisation of live Bitcoin transactions from the Blockchain
4 stars based on
36 reviews
What can I do with the multiexplorer API? The Multiexplorer API can be used to create a cryptocurrency wallet that is both lightweight meaning it doesn not use large amounts of bandwidth, memory and hard drive space and decentralized.
Doesn't building a wallet that depends on an expernal service make it centralized? Only if that wallet was dependent on that one service. Can I run my own multiexplorer API?
Yes, all the software that runs the multiexplorer API is open source and available on Github. Who decides which services get bitcoin block explorer live here? The operators of multiexplorer. If you run your own instance of multiexplorer, you can disable certain services and bitcoin block explorer live your own set. Use a single blockexplorer API via multiexplorer bitcoin block explorer live a pass-thtough.
This parameter can be used to call a single survice, or it can be used to enable various "fetching modes". Each currency has an ordered list of defined services. Using this mode guarantees a result from somewhere will always be returned. This service can be thought as being "high availability". This will call N services, and verify that they all return the same data. If any service returns a different value, the call will indicate this. In the case of a paranoid mode failure, the underlying cryptocurrency network may be forked.
This mode is helpful for determining the optimal transaction fee and current price. This mode does not apply to many blockchain operations since all services return the exact same data. One service will be used for each addresses passed in. All calls will be spread out over N number of seconds.
The higher value of N passed throug, the higher level of privacy achieved. Max value for N is Note, "paranoid mode" and "private mode" does not apply in the context of current price. The currency argument is required. Enter three leter cryptocurrency code. The fiat argument is required.
Enter three leter fiat currency code. The time argument is bitcoin block explorer live required. It an be either an ISO date or unix timestamp. Note, "average mode" does not apply in the context of address balance.
The currency argument is optional. If you leave it off, the currency will be guessed from decoding the address version byte. Note, "average mode" does not apply in the context of unspent outputs. Note, "average mode" does not apply in the context of historical transactions. The fiat option is optional and will return the fiat price at the time of the transaction being confirmed. Only applicable when extended fetch is enabled The data that comes out of this endpoint is meant for use in wallet UIs to show activity from addresses.
It is not meant to be used in creation of transactions. Setting it to true will include the response as it was returned directly from the service. Note, "average mode" does not apply in the context of a transaction. Note, "average mode" does not apply in the context of block information. Bitcoin block explorer live is no way to infer the currency from the block hash or block height, unlike from address version byte.
Note, only bitcoin block explorer live mode" applies for the optimal fee bitcoin block explorer live. Each service returns a different value, so it makes sense to use the value of each service averaged together. Paranoid mode will always fail, because rarely do each service return the exact same recommended fee. Must be 3 or 4 letter code. Returned is the amount of satoshi's that should be added as a transaction fee per KiB bytes.
Must be 3 or 4 letter cryptocurrency code. Returned is txid of the newly pushed transaction. Fields included in POST body must be: Returned is always "OK" if completed successfully. TXID can be full or partial.