Blockstream Esplora

• Check for a paymentHas this address been paid, and is the payment safe to act on yet? Answers with a true or false a branch step can read, plus how much arrived and how deeply confirmed it is. Money still in the mempool is reported separately and never counted, because an unconfirmed payment can still be replaced. The step to put in front of 'send the goods'. No API key required.
• Get an address's balanceWhat a Bitcoin address holds right now, what it has ever received and sent, and what is still on its way. Amounts come back in both satoshis and BTC, and unconfirmed money is kept separate from the balance. No API key required.
• List an address's transactionsAn address's history, newest first, with how much each transaction paid it and how much it spent. Narrow it to confirmed or pending, or to a date range. Ask for up to 100 and you get 100 - the paging underneath is handled for you. No API key required.
• List an address's coinsThe individual coins an address is holding - its unspent outputs - newest first, with what each is worth and how deeply confirmed it is, plus their total. What a wallet would have to spend from. No API key required.
• Get a transactionOne transaction in full: who it paid and how much, what it spent to do it, the fee and fee rate, and how many confirmations deep it is. The scripts and signatures are left out - Get a transaction's raw data has those. No API key required.
• Check if a transaction is confirmedWhether a transaction has made it into a block yet, and how many confirmations deep it is. The light step to run on a schedule while waiting for a payment to settle. No API key required.
• Get a transaction's raw dataA transaction exactly as it sits on the chain, in hex. What to hand to a wallet, an analyser, or the Broadcast step when a transaction needs sending again. No API key required.
• Check if a transaction's outputs are spentWhether the money a transaction paid out is still sitting there, output by output, and which transaction moved each one on. How a workflow follows the money, or notices that a coin it was watching has gone. No API key required.
• Broadcast a signed transactionSend a transaction your wallet has already signed to the Bitcoin network, and get its transaction ID back. This is the one step here that changes anything, and it cannot be undone once the network has it. Nothing is signed for you and no key is ever held - if the transaction is not already signed, the network rejects it. No API key required.
• Get a blockOne block: when it was mined, how much is in it, and how deep in the chain it now sits. Name it by height or by hash - the field takes either - or leave it blank for the newest block, which is how a workflow checks the chain is moving. No API key required.
• List recent blocksThe most recently mined blocks, newest first, with when each was mined and what is in it. Start from a height to walk back through the chain instead. No API key required.
• List a block's transactionsEverything a block confirmed, in the order it was mined, with each transaction's fee and size. The first one is always the miner claiming the block's reward. No API key required.
• Get current feesWhat to pay right now to confirm in the next block, within half an hour, within an hour, or within a day - in satoshis per virtual byte, which is how Bitcoin fees are quoted. Check it before building a transaction, or to hold a payment back until the network is cheap. No API key required.
• Check how busy the network isHow many transactions are waiting to be confirmed, how many blocks' worth that is, and the range of fees they are paying. The step that tells a workflow whether now is a good moment to send something. No API key required.
• List transactions just broadcastThe last transactions the network saw, before any of them are in a block, with what each is paying in fees. A live sample of what is going on right now. No API key required.

No actions match that.