Satoshi Converter
Convert BTC, mBTC, μBTC and satoshis instantly without floating-point rounding. Copy exact results and check whole-satoshi limits.
- Input / output
- BTC, mBTC, bits and satoshis → selected denomination
- Test state
- Passed
- Last tested
Bitcoin (BTC)
Bitcoin is a decentralized peer-to-peer monetary network, and BTC is its native digital asset. Bitcoin transactions spend and create UTXOs; miners use proof of work to propose blocks, while fully validating nodes independently check blocks and transactions against Bitcoin’s consensus rules.
BitcoinToolkit separates CoinGecko’s aggregated USD reference from the Binance Spot BTC/USDT market, shows the source and age of each dataset, and connects market information to an exact BTC–satoshi converter and sourced explanations of fees, address formats and confirmations.
- Snapshot:
- CoinGecko · USD
- Chart:
- Binance Spot · BTC/USDT
- Timezone:
- UTC
Use this page to check reference market data, convert Bitcoin units and understand how Bitcoin transactions work. It is educational reference material—not an executable exchange quote or a trading recommendation.
Content ownership: BitcoinToolkit Editorial Team
Editorial Review: BitcoinToolkit Editorial Team
Technical references: Bitcoin Core documentation, the Bitcoin Core repository and relevant BIPs.
Review approach: Technical explanations are checked against primary technical sources.
Last content review: Data integration last tested:
Bitcoin Candlestick Chart
BTC/USDT · Binance Spot · UTC
Long ranges automatically use a compatible candle interval so the chart stays within the supported candle limit.
Historical Binance Spot candles are available. JavaScript is required for current-candle updates.
Recent OHLC and volume data
| Time (UTC) | Open (USDT) | High (USDT) | Low (USDT) | Close (USDT) | Volume (BTC) |
|---|---|---|---|---|---|
| Aug 25, 2026 10:00:00 UTC | 79,187.20 USDT | 79,429.94 USDT | 78,992.00 USDT | 79,300.00 USDT | 586.75 BTC |
| Aug 25, 2026 09:00:00 UTC | 79,930.76 USDT | 79,958.00 USDT | 78,888.00 USDT | 79,187.20 USDT | 1,475.29 BTC |
| Aug 25, 2026 08:00:00 UTC | 79,705.79 USDT | 80,249.00 USDT | 79,622.00 USDT | 79,930.77 USDT | 788.32 BTC |
| Aug 25, 2026 07:00:00 UTC | 80,574.09 USDT | 80,819.67 USDT | 79,369.17 USDT | 79,705.79 USDT | 1,307.68 BTC |
| Aug 25, 2026 06:00:00 UTC | 80,731.90 USDT | 80,923.69 USDT | 80,420.00 USDT | 80,574.09 USDT | 745.40 BTC |
Market data: Binance Spot BTC/USDT
Charting library: TradingView Lightweight Charts
Bitcoin at a Glance
SymbolBTC
NetworkBitcoin
Asset TypeNative cryptocurrency
Ledger ModelUTXO
ConsensusProof of Work
Smallest UnitSatoshi
Units per BTC100,000,000 satoshis
Fee Unitsatoshis per virtual byte (sat/vB)
Common Address Prefixes1, 3, bc1q, bc1p
Typical Block IntervalAbout 10 minutes on average
Bitcoin targets an average block interval of about ten minutes; individual blocks can arrive sooner or later.
Protocol references: Bitcoin Core documentation and relevant BIPs.
Bitcoin Tools
Converters
Bitcoin Calculators
Stablecoin Transfer Fee Calculator
Estimate USDC, USDT and DAI transfer fees across verified networks. Compare fee assets, cost ranges, fee percentages and sender total cost.
- Input / output
- BTC, mBTC, bits and satoshis → selected denomination
- Test state
- Passed
- Last tested
Bitcoin Units [2]
One bitcoin equals 100,000,000 satoshis, and changing the display denomination does not change the underlying amount.
Base unit1BTC
The base display unit commonly used for whole-bitcoin amounts.
=1,000mBTC
One millibitcoin is one thousandth of a bitcoin.
=1,000,000bits / μBTC
One bit or microbitcoin is one millionth of a bitcoin.
=100,000,000satoshis
A satoshi is the smallest native Bitcoin unit.
Wallets and services may display the same amount in BTC, mBTC, bits or satoshis. Changing the display unit does not change the underlying Bitcoin amount. Decimal precision and rounding rules matter when a value is converted or copied between systems.
Example
0.001 BTC equals 100,000 satoshis.
Common mistake
A display-unit change does not change the underlying amount.
Compatibility note
Wallets and services may support different display units and decimal precision.
Bitcoin transaction fees are determined mainly by virtual size and fee rate, not by the amount of BTC being sent.
- Select UTXOsThe wallet chooses spendable transaction outputs as inputs.
- Recipient outputThe transaction assigns value to the recipient script.
- Change outputUnspent input value returns to a wallet-controlled output.
- Set feeThe wallet chooses a fee rate based mainly on transaction virtual size.
- SignRequired keys authorize the selected inputs.
- BroadcastPeers validate and relay the transaction.
- Block inclusionA miner may include the transaction in a candidate block.
- ConfirmationEach accepted block above it adds another confirmation.
Bitcoin does not maintain a traditional account balance. Wallet software totals spendable UTXOs, then creates inputs and outputs for a new transaction. Transaction fees are determined mainly by the transaction’s virtual size, measured in vbytes, and the selected fee rate, measured in sat/vB. The amount of bitcoin being sent is not the main factor. Block discovery is probabilistic, so a specific confirmation time cannot be guaranteed.
Example
A wallet can spend two UTXOs, create one recipient output and return change in a second output.
Common mistake
The bitcoin amount sent is not the main determinant of the fee.
Compatibility note
Fee estimation and replace-by-fee support vary by wallet and receiving service.
Bitcoin address prefixes indicate an encoding or output type, but they do not prove ownership, identity or balance.
| Address Type | Common Prefix | Encoding | Typical Use | Compatibility Note |
|---|---|---|---|---|
| Legacy | 1 | Base58Check | Older pay-to-public-key-hash destinations. | Broad compatibility, but usually less block-space efficient. |
| P2SH | 3 | Base58Check | Script-hash destinations; often used for nested SegWit, but not exclusively. | The prefix does not reveal the redeem script inside it. |
| Native SegWit v0 | bc1q | Bech32 | Native version 0 SegWit destinations. | Requires Bech32 support; usually more efficient than legacy formats. |
| Taproot / SegWit v1 | bc1p | Bech32m | Taproot version 1 SegWit destinations. | Requires wallet and service support for Taproot addresses. |
A 3 prefix identifies a P2SH address, not the exact redeem script inside it. An address prefix does not prove ownership, identity or balance.
Example
A mainnet address beginning with 3 identifies P2SH, not the redeem script inside it.
Common mistake
A prefix cannot establish ownership, identity or balance.
Compatibility note
Confirm that the sending wallet supports the recipient address encoding.
What Bitcoin Confirmations Mean [2]
A Bitcoin confirmation means that a transaction has been included in an accepted block; additional accepted blocks make some forms of reversal progressively less likely.
0 confirmations
The transaction is visible to peers but is not yet included in a block and may still be replaced or rejected.
1 confirmation
The transaction is included in a block, but acceptance still depends on the receiving service and risk context.
Multiple confirmations
Additional blocks make reversal progressively less likely; required counts differ by service policy and amount.
Bitcoin block timing is probabilistic rather than scheduled. A fee rate can affect a transaction’s relative priority, but it cannot guarantee the next block. Receiving services choose their own acceptance thresholds based on amount and risk. Additional confirmations reduce some reversal risks, but they do not correct an address mistake, recover compromised keys or remove other operational risks.
Example
A transaction in a block has one confirmation; the next accepted block makes it two.
Common mistake
A higher fee rate can improve priority but cannot guarantee a confirmation time.
Compatibility note
Exchanges, wallets and merchants set different acceptance policies.
Start Learning Bitcoin
These published guides explain the concepts used by the tool and reference sections on this page.
- 01
What Is a Satoshi?
Start with the exact relationship between BTC and its smallest unit.
- 02
How Bitcoin Transaction Fees Work
Continue to virtual size, fee rates, mempool demand and uncertain confirmation timing.
- 03
Bitcoin Address Types Explained
Then compare address encodings, prefixes, compatibility and safe interpretation.
How This Page Was Checked
These checks describe the review performed for this published page. No automated pass count or run ID is claimed.
- Protocol source review
- Address format reference review
- Unit conversion tests
- CoinGecko response validation
- Binance REST candle validation
- Binance WebSocket message validation
- Missing-data handling
- UTC timestamp handling
Market Data Methodology
The market snapshot is requested server-side from CoinGecko as aggregated USD data and stored in an approximately 60-second site cache. Candles are requested from Binance Spot for BTC/USDT, and a matching public stream updates the current candle only after the kline message and candle values pass validation. All market timestamps are shown in UTC.
The snapshot is CoinGecko aggregated USD data. The chart is Binance Spot BTC/USDT data. Their providers, venue coverage and quote currencies differ, so displayed values can differ.
- Market Snapshot Source
- CoinGecko aggregated market data (USD)
- Candlestick Source
- Binance Spot market data
- Pair
- BTC/USDT
- Venue
- Binance Spot
- Market Type
- Spot
- Timezone
- UTC
- Cache
- Snapshot cache is approximately 60 seconds; historical candle cache varies by interval.
- Failure Handling
- Verified cache is labeled Cached or Delayed. Missing values remain unavailable.
- Snapshot Status
- Fresh
- Chart Status
- Historical Only
- Report Issue
- Report a market-data problem →
Known Limitations
- CoinGecko snapshot is not an executable exchange quote.
- Binance chart represents BTC/USDT on Binance Spot only.
- Historical candles may remain available during a current-candle stream failure.
- Address prefixes do not prove ownership, identity or balance.
- Fee rate cannot guarantee a specific confirmation time.
- BitcoinToolkit does not publish price predictions or buy/sell signals.
Technical Sources
Protocol claims are checked against primary Bitcoin references. Market values and candles are attributed to their separate providers.
Bitcoin protocol references
Market data policy
Bitcoin FAQ
Answers to common questions about the market reference and Bitcoin network concepts used on this page.
Is the CoinGecko USD reference price the same as the Binance candle price?
No. The snapshot is CoinGecko aggregated USD data, while the chart is Binance Spot BTC/USDT. Their sources, venue coverage and quote currencies differ, so values can differ.
How current is the market snapshot?
The page shows the provider time, when BitcoinToolkit fetched the response, dynamic data age and a state of Fresh, Cached, Delayed or Unavailable.
What happens if a market API is unavailable?
Verified cached values may remain visible with Cached or Delayed labels. If no validated data exists, the field remains Unavailable; the page does not substitute zeros or fabricated values.
Does this page predict Bitcoin prices?
No. It provides sourced reference data, practical tools and network explanations, not price predictions or buy/sell signals.
Why can confirmation time vary?
Block discovery is probabilistic, mempool conditions change and receiving services use different acceptance policies. A selected fee rate cannot guarantee a confirmation time.
Does an address prefix identify its owner?
No. A prefix indicates an address encoding or output type. It does not prove ownership, identity or balance, and a 3 prefix does not reveal the P2SH redeem script.
Editorial Information
Verified technical content, reviewed sources and update history.
- Published
- Last Review
- Data Verification
- Sources
- Official documentation