Mempool.space

• Get the bitcoin priceGet what one bitcoin is worth right now, in your choice of seven currencies - and in all seven at once, so one step can price a report for several regions. The number behind a daily price post, a portfolio total or a threshold alert. No API key required.
• Get the bitcoin price on a dateGet what one bitcoin was worth at a past moment. Pick the date and time and this finds the closest price mempool.space has, and tells you which moment that price is from. The step to put after 'Get a transaction' to value a payment at the moment it confirmed, for a ledger, an invoice or a tax record. No API key required.
• Get recommended feesGet what a Bitcoin transaction needs to pay right now to confirm, at each level of hurry - next block, within half an hour, within an hour, and the two economy rates. All in sat/vB, the unit every wallet asks for. Fees swing by an order of magnitude in a day, so this is the step behind 'send when it's cheap' and 'tell me when fees spike'. No API key required.
• Check network congestionCheck how busy Bitcoin is: how many transactions are waiting to be mined, how much room they need, and how many blocks it would take to clear them. When the backlog is deep, cheap transactions wait - so this is the step to check before sending anything, or to post to a channel when the network gets busy. No API key required.
• Get network statusGet the health of the Bitcoin network: how much computing power is securing it, how hard mining currently is, and when the difficulty next changes and by how much. Difficulty adjusts every two weeks and the estimate moves all the way up to the day, so this is the step behind a mining report or a network dashboard. No API key required.
• List mining poolsList the mining pools that found Bitcoin's blocks over a period you choose, ranked by how many they mined and what share of the network that is. Mining concentration is the number people watch about Bitcoin's health, and it shifts week to week - so this is the step behind a mining report or a concentration alert. No API key required.
• Get an address balanceGet what a Bitcoin address holds and what has passed through it: its balance, everything ever received and sent, and how many transactions have touched it. Money still waiting to confirm is reported separately from money that has settled, because only one of them is yours to spend. The step behind a treasury report or a 'has the payment arrived' check. No API key required.
• List an address's transactionsList the most recent transactions at a Bitcoin address, newest first, with what each one moved and how many confirmations it has. Include the ones still waiting to confirm and you see a payment the moment it is broadcast, rather than ten minutes later. The step to run on a schedule to watch an address for incoming money. No API key required.
• List an address's unspent coinsList the individual coins sitting at a Bitcoin address, each with its own value and how many confirmations it has, plus what they add up to. Bitcoin holds a balance as separate coins rather than one number, and a wallet has to spend whole ones - so this is what a spend actually has to work with, and what a coin-management or consolidation workflow reads. Addresses holding more than 500 coins are more than mempool.space's public API will list; 'Get an address balance' still counts them. No API key required.
• Check an address is validCheck whether a Bitcoin address is real before anything is sent to it, and find out what kind it is. Bitcoin payments cannot be reversed and a mistyped address is money gone, so this is the step to put in front of one. An invalid address is an answer here, not a failure, so a workflow can branch on it and stop. No API key required.
• Get a transactionGet one Bitcoin transaction: whether it has confirmed and how many times, what it moved and between which addresses, and what it paid in fees. The step behind 'wait for three confirmations before shipping' and 'did that payment actually go through'. No API key required.
• Check whether outputs have been spentCheck, for each of a transaction's outputs, whether the money has been moved on again - and by which transaction. The step that answers 'has the recipient touched what we sent them' and 'is that coin still where we left it', which a balance alone cannot tell you. No API key required.
• Get a blockGet one block by its height or its hash: when it was mined, which pool found it, how many transactions it settled and what they paid. Paste whichever of the two you have - it works out which. No API key required.
• List recent blocksList the blocks most recently mined, newest first, each with its miner, its fees and how many transactions it settled. A block arrives about every ten minutes, so this is what a 'what's happened on Bitcoin lately' digest reads, and how a workflow notices a new block. No API key required.
• List a block's transactionsList the transactions settled in one block, in the order they were mined, a page at a time. The first is always the miner's own reward. Blocks hold thousands of transactions, so this is the step to loop over when auditing what a block moved. No API key required.

No actions match that.