Bitcoin Wiki - User contributions [en]

Category:Block chain browsers

2021-11-11T15:18:33Z

Wiz: /* List of online Bitcoin block chain browsers */

A Bitcoin [[block chain browser]] is an application, typically web-based, that allow users to search and navigate the Bitcoin [[block chain]].

Note that using block chain browsers to check addresses under your control or to which you have sent money can be problematic for your [[privacy]].

It can be a good idea to get software such as [https://github.com/janoside/btc-rpc-explorer BTC RPC Explorer] and run that on hardware that you control yourself, and connect it to your own [[full node]].

If you do need to use a 3rd party block explorer, do it through a [[Tor]] onion service. For example [[Blockstream]]'s explorer is reachable at http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion/ - or less ideal, through a VPN.

== List of online Bitcoin block chain browsers ==

=== 2020 ===
* https://mempool.space/
* https://bitinfocharts.com/bitcoin/explorer/
* blockchains.io/
* blockonomics.co/
* blockseer.com/
* btc.bitaps.com/
* chain.localbitcoins.com/
* chain.so/
* chainflyer.bitflyer.jp
* https://bitaps.com/
* https://blockpath.com/
* https://blockstream.info/
* https://btc.com/
* https://chaindex.com/blockchain/
* https://explorer.btc21.org/
* https://learnmeabitcoin.com/explorer/node/
* https://live.blockcypher.com/
* https://oxt.me/
* https://sochain.com/btc
* https://www.kycp.org/
* https://www.localbitcoinschain.com/
* https://www.oklink.com/
* https://www.smartbit.com.au/
* https://yogh.io/
* insight.bitpay.com
* live.blockcypher.com/btc/
* scorechain.com/
* tradeblock.com/blockchain
* http://blockchainsql.io/

Local app:
* orange - local electron app

=== Older list ===
* [https://apirone.com/btc/ Bitcoin Block Explorer with SegWit support]
* [https://btc.bitaps.com Bitcoin Block Explorer]
* [https://bitinfocharts.com/bitcoin/explorer/ BitInfoCharts]
* [https://blockexplorer.com/ Bitcoin Block Explorer]
* [https://bitcoinchain.com/block_explorer/ BitcoinChain]
* [https://bitupper.com/en/explorer/bitcoin Bitupper Explorer]
* [https://btc.blockchainhub.co.jp BlockhainHub]
* [https://www.biteasy.com/blockchain/blocks bitEasy]
* [https://blockchain.info/ Blockchain.info]
* [https://live.blockcypher.com/ BlockCypher]
* [https://www.blockonomics.co/ Blockonomics]
* [https://blockpath.com/ Blockpath]
* [https://btc.blockr.io/ blockr]
* [https://www.blocktrail.com/BTC BlockTrail]
* [https://chain.btc.com/ BTC Chain]
* [http://chainflyer.bitflyer.jp/ chainFlyer]
* [http://coinbelly.io/ Coinbelly]
* [https://explorer.coinpayments.net/ CoinPayments]
* [https://www.coinprism.info/ Coinprism]
* [http://learnmeabitcoin.com/explorer/ learnmeabitcoin]
* [https://chain.localbitcoins.com/ LocalBitcoins]
* [https://smartbit.com.au Smartbit]
* [https://chain.so/btc SoChain]
* [https://tradeblock.com/blockchain/ TradeBlock]
* [https://www.walletexplorer.com/ WalletExplorer]
* [http://webbtc.com/ webBTC]
* [https://chaindex.com/blockchain/ chaindex]
* [https://BTC.com BTC.com]

== List of online block chain browsers (testnet3) ==
* [https://tbtc.bitaps.com/ Testnet explorer]
* [https://tbtc.blockr.io/ blockr]
* [https://tchain.btc.com/ BTC Chain]
* [https://sandbox.smartbit.com.au/ Smartbit]

Bech32 adoption

2021-11-11T15:16:23Z

Wiz: /* Blockchain Explorers */

[[Bech32]] is a bitcoin [[address]] format specified by [[BIP 0173]]. It is used for the native segwit version 0 output types, P2WPKH and P2WSH. The upcoming [[Taproot]] softfork will add another output type called Pay to Taproot (P2TR). P2TR outputs and future native segwit versions will be using an updated variant of [[Bech32]], called [[Bech32m]] (specified by [[BIP 0350]]). This page tracks the adoption of [[Bech32]] and [[Bech32m]].

Ideally wallets and services would first support ''sending to'' new addresses. When most wallets and services support sending to the new address type, people are more likely to adopt it for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Bitcoin Core || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} || Uses P2WPKH as default address since version [https://bitcoin.org/en/release/v0.20.0 0.20.0]. Creating P2TR addresses requires manual import for now.
|-
| Bitcoin Knots || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Acceptable|Starting with 22.0}} ||
|-
| bcoin || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Electrum || {{Yes}} || {{Yes}} || {{Yes|Since 4.1.0}} || {{Evaluating|??}} ||
|-
| Armory || {{Yes}} || {{No}} || {{Planned|Planned around activation}} || {{Evaluating|??}} ||
|-
| JoinMarket || {{Yes}} || {{Yes}} || {{Evaluating|Depends on python-bitcointx}} || {{Evaluating|??}} ||
|-
| Blockstream Green || {{Yes}} || {{Yes}} || {{Yes|Mobile 3.7.6+, Desktop 1.0.4+}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47]
|-
| Breadwallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/BRDapp/comments/9xx1hq/as_of_today_brd_fully_supports_native_segwit/
|-
| Samourai Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || {{No|Currently not planned}} || https://twitter.com/SamouraiWallet/status/1415788631491497985?s=20
|-
| Coinomi || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| BTC.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Casa || {{Yes}} || {{No}} || {{Planned}} || {{Planned}} ||
|-
| Mycelium || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} || {{Planned|Planned before activation}} || {{Evaluating|??}} ||
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned: via NBitcoin before Activation}} || {{Planned|Planned: via NBitcoin before Activation}} || https://twitter.com/NicolasDorier/status/1413693010236170241
|-
| Trust Wallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://twitter.com/GuardaWallet/status/1194270398730448896 twitter announcement]
|-
| Bisq || {{Yes}} || {{Yes}} || {{Evaluating|Dependent on BitcoinJ}} || {{Evaluating|??}} || As of v1.5.0 https://bisq.network/blog/bisq-v1.5.0-highlights/
|-
| Muun || {{Yes}} || {{Yes}} || {{Planned|Before activation}} || {{Planned|After activation}} || https://twitter.com/MuunWallet/status/1415692517690023937
|-
| BlueWallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Sparrow Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/SparrowWallet/status/1415632270434705408
|-
| Specter Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benkaufman/status/1431293856675508228
|-
| C-Lightning || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} ||
|-
| Fully Noded || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Since v0.2.26}} || https://twitter.com/FullyNoded/status/1438652812410298370
|-
| [https://github.com/unchained-capital/caravan Caravan] || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| AQUA || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| LND || {{Yes}} || {{Yes}} || {{Planned|Planned: via btcsuite}} || {{Evaluating|??}} ||
|-
| Exodus || {{Yes}} || {{Yes}} || {{Planned|Planned before activation, depends on bitcoinjs}} || {{No|Not yet planned}} ||
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Trezor Suite || {{Yes}} || {{Yes}} || {{Planned|Planned: before Activation}} || {{Planned|Planned: after Activation}} || https://twitter.com/pavolrusnak/status/1413790070205734916
|-
| Ledger Live (desktop app) || {{Yes}} || {{Yes}} || {{Planned|Planned: at activation}} || {{Planned|Planned: at activation}} || [https://twitter.com/darosior/status/1432371465815568390 Announced at Surfin' Bitcoin]
|-
| KeepKey chrome app || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Ballet + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Tangem + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockstream Jade + Blockstream Green || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47] available via Blockstream Green mobile apps 3.7.6+ and desktop app 1.0.4+
|}

=== Web Wallets ===

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitGo || {{Yes}} || {{Yes}} || {{Planned|Before activation|}} || {{Planned}} || Full support on v2 platform, no plans to add support on v1 platform. Also see: https://blog.bitgo.com/native-segwit-addresses-via-bitgos-api-4946f2007be9
|-
| blockchain.com web|| {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://twitter.com/Pellicceama/status/1436324051803414535
|-
| HolyTransaction || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || open source JavaScript implementation
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/GuardaWallet/status/1194270398730448896
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://1fox.com/?c=en/content/blog&id=12
|-
| [[AgoraDesk]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Anycoin Direct || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| BitBargain.co.uk || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitcoinblog.de/2018/08/10/bitcoin-de-aktiviert-segwit-kunden-sparen-gebuehren/
|-
| Bitfinex || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/bitfinex/status/1189164144789983234
|-
| BitMEX || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://blog.bitmex.com/introducing-bech32-deposits-on-bitmex-to-deepen-bitcoin-integration-lower-fees/
|-
| Bittrex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/gqt1m6/bittrex_does_not_even_support_withdrawals_to/
|-
| Bittylicious || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
|-
| Bitso || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bitso/status/1203784055340314624?s=20
|-
| Bitwage || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BSDEX || {{Yes}} || {{No}} || {{Evaluating|??}} || {{No}} ||
|-
| CardCoins.co || {{Yes}} || No deposits || {{Yes}} || No deposits || https://twitter.com/CardCoinsCo/status/1452680654030872589
|-
| CEX.IO || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinbase.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/diogorsergio/status/983052769262292992 (Note that Coinbase commerce does not support sending to bech32)
|-
| CoinFalcon || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinfloor || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinfloor.zendesk.com/hc/en-us/articles/360018072678-Why-are-there-2-BTC-deposit-addresses-to-choose-from-
|-
| [https://coinmate.io Coinmate.io] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinmate.io/blog/important-coinmate-update/
|-
| Coinsbank.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinygram || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Flyp.me || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| GDax || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Globitex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| HitBTC || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Independent Reserve|| {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.independentreserve.com/bitcoin/investing
|-
| Itbit || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Kraken || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/krakenfx/status/1060306827848470528
|-
| LedgerX || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Liberalcoins || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://liberalcoins.com
|-
| [[LocalBitcoins]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/LocalBitcoins/status/1322194709159301120
|-
| Luno || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.luno.com/blog/en/post/luno-launches-support-for-bech32-addresses
|-
| Paxful.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://paxful.com/support/en-us/articles/360011766520-Can-I-Withdraw-Bitcoin-from-Paxful-Wallet-to-My-External-Wallet-
|-
| Poloniex.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| River.com || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || {{Evaluating|??}} ||
|-
| Square CashApp || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/TheRockTrading/status/976787499648512003
|-
| Walltime || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://walltime.info
|-
| Purse.io || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| www.bitwala.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Xapo || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| GenesisCoin || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| General Bytes || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Depending on configuration. Since version 20190613 https://www.generalbytes.com/en/support/changelog
|-
| Lamassu Douro || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@LamassuSupport/announcing-crafty-chnemu-v7-3-9522fe2868
|}

=== Blockchain Explorers ===

To investigate bech32 capability, you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code> or look up the addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

To verify bech32m readiness, you can look up the mainnet TXID <code>b10c007c60e14f9d087e0291d4d0c7869697c6681d979c6639dbd960792b4d41</code> on which the first output should be addressed as <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqsyjer9e</code>. Note that the superseded bech32 encoding only differs in the last six characters that encode the checksum: <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqs_3wf0qm_</code>.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display Bech32 !! Index Bech32 !! Display Bech32m !! Index Bech32m !! Notes
|-
| bitaps.com || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp
|-
| Blockbook || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://btc3.trezor.io
|-
| blockchain.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.blockchain.com/explorer
|-
| Blockchair || {{Yes}} || {{Yes}} || {{Planned}} || {{Planned}} || https://github.com/Blockchair/Blockchair.Support/issues/567#issuecomment-890016344
|-
| Blockcypher || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://blockpath.com
|-
| BTC.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://BTC.com
|-
| Esplora || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances are https://blockstream.info/ and https://www.localbitcoinschain.com/. [https://github.com/Blockstream/esplora/issues/323 Issue] for BIP350 support.
|-
| Insight || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Open source explorer, instances include https://insight.bitpay.com/
|-
| Mempool || {{Yes}} || {{Yes}} || {{Acceptable|On test instance}} || {{Acceptable|On test instance}} || Open source explorer, instances include https://mempool.space https://mempool.ninja https://mempool.emzy.de https://mempool.bisq.services https://mempool.bitcoin.ninja https://mempool.bitaroo.net/
|-
| OXT || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://oxt.me/
|-
| Tradeblock || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://tradeblock.com/bitcoin
|-
| WalletExplorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://walletexplorer.com/
|-
| Bitcoin Explorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitcoinexplorer.org, https://twitter.com/BitcoinExplorer/status/1425148093977309187
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! P2WPKH/P2WSH Invoices !! Bech32 Withdrawal addresses !! P2TR Invoices !! Bech32m Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment notifications, merchant dashboard, plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://btcpayserver.org BTCPay Server] || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Supported since 1.3.0}} || https://twitter.com/NicolasDorier/status/1432354289599451136, https://twitter.com/NicolasDorier/status/1457527754350415873
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://confirmo.net CONFIRMO] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://cryptochill.com CryptoChill] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Highly customizable Bitcoin and Lightning Network payment gateway. Multi-sig, HD wallets, API, SDK.
|}

=== Mining Pools ===

{| class="wikitable sortable"
|-
! Name !! Payout to Bech32 !! Payout to Bech32m !! Notes
|-
| [https://pool.btc.com/ BTC.com Pool] || {{No}} || {{Evaluating|??}} ||
|-
| [http://ckpool.org/ Ckpool] || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://kano.is/ KanoPool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=789369.msg53374508#msg53374508 bitcointalk source]
|-
| [http://poolin.com/ Poolin] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5169994.msg52184844#msg52184844 bitcointalk source]
|-
| [https://sbicrypto.com SBICrypto Pool] || {{Yes}} || {{Acceptable|Ready to release at activation}} ||
|-
| [https://slushpool.com/ Slush Pool] || {{Yes}} || {{Planned|At activation}} || [https://twitter.com/braiins_systems/status/1432376840484794375 Tweet]
|-
| [https://ukrpool.com/ Ukr Pool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5124825.msg51358033#msg51358033 bitcointalk source]
|-
| [https://pool.viabtc.com/ ViaBTC Pool] || {{No}} || {{Evaluating|??}} ||
|}

=== Libraries ===

{| class="wikitable sortable"
|-
! Name !! Language !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| [https://github.com/bitcoin/libbase58 libbase58] || C || {{No}} || n/a || {{No}} || n/a
|-
| [https://github.com/MetacoSA/NBitcoin NBitcoin] || .NET || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354289599451136
|-
| [https://github.com/bcoin-org/bcoin bcoin] || JS || {{Yes}} || {{Yes}} || {{Planned|In Review}} || {{Evaluating|??}} || https://github.com/bcoin-org/bcoin/pull/1038
|-
| [https://github.com/btcsuite btcsuite/btcutil] || Go || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/btcsuite/btcutil/pull/202
|-
| [https://github.com/bitcoinjs/bitcoinjs-lib bitcoinjs-lib] || JS || {{Yes}} || {{Yes}} || {{Acceptable|Merged but unreleased}} || {{Evaluating|??}} || https://github.com/bitcoinjs/bitcoinjs-lib/issues/1522#issuecomment-887468902
|-
| [https://bitcoinj.github.io/ bitcoinj] || Java || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bitcoinj/bitcoinj/commit/183986c9801f10f1bf46bd46621e535973d39ef8
|-
| [https://github.com/bitcoin-s/bitcoin-s-core bitcoin-s] || Scala || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Around activation}} || https://twitter.com/benthecarman/status/1415741934992232457
|-
| [https://github.com/rust-bitcoin/rust-bitcoin rust-bitcoin] || Rust || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/RCasatta/status/1423695925252329476
|-
| [https://lightningdevkit.org Lightning Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|Pending BOLT update}} ||
|-
| [https://bitcoindevkit.org Bitcoin Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Planned|WIP}} || {{Planned|WIP}} || https://docs.rs/bdk
|-
| [https://github.com/ElementsProject/libwally-core libwally-core] || C || {{Yes}} || {{Yes}} || {{Yes|Since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} || {{Yes|Since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} ||
|-
| [https://github.com/Blockstream/gdk GDK] || C || {{Yes}} || {{Yes}} || {{Yes|Since [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 0.0.47]}} || {{Evaluating|??}} ||
|-
| [https://github.com/Simplexum/python-bitcointx python-bitcointx] || Python || {{Yes}} || {{Yes}} || {{Planned|WIP}} || {{Planned|WIP}} || https://github.com/Simplexum/python-bitcointx/issues/57
|-
| [https://github.com/dgarage/NBXplorer/ NBXPlorer] || C# || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354822888431619
|-
| [https://github.com/acinq/bitcoin-kmp Kotlin Multiplatform Bitcoin Library] || Kotlin || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} || https://twitter.com/realtbast/status/1458533450919649284
|-
| [https://github.com/libbitcoin Libbitcoin] || C++ || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}


=== References ===

[[Category:Software]]

Signet

2021-02-22T14:48:30Z

Wiz:

'''Signet''' ([[BIP 0325]]) is a new test network for Bitcoin which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net VI" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signetchallenge=<hex></code>, and preferably also at least one seed node using <code>-signetseednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1598918400, nonce 52613770, and difficulty 0x1e0377ae.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

NOTE: signet (IV) was merged into the master branch of Bitcoin Core as of https://github.com/bitcoin/bitcoin/pull/18267

===Fetch and compile signet===

<pre>
$ git clone https://github.com/bitcoin/bitcoin
$ cd bitcoin
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/18267 Pull request #18267 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/
* https://mempool.space/signet

==Custom Signet==

'''NOTE:''' Until it is merged into master branch, you may first need to check-out (or merge) the code referred in https://github.com/bitcoin/bitcoin/pull/19937 in order to get the script <code>contrib/signet/miner</code>.

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a regtest node and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -regtest -daemon -wallet="test"
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey
"pubkey": "THE_REAL_PUBKEY",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>THE_REAL_PUBKEY</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>THE_REAL_PUBKEY</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signetchallenge</code> value becomes <code>5121...51ae</code>. Where <code>...</code> stands for <code>THE_REAL_PUBKEY</code> (see above).

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -regtest stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signetchallenge=5121...51ae # fill in THE_REAL_PUBKEY" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir -wallet="test"
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we're going to get an issuer up and running to mine blocks.

We'll need to provide a value for <code>nbits</code> which is the mining target and is inversely proportional to the difficulty. This will allow us to set the average time between mined blocks.

We can use the <code>calibrate</code> command to give us the <code>nbits</code> for an average mining time of 10 min (600 s):

<pre>
$ ../contrib/signet/miner --cli="./bitcoin-cli" calibrate --grind-cmd="./bitcoin-util grind" --seconds=600
</pre>

Referring to our <code>nbits</code> value with the variable <code>$NBITS</code>, we need to specify <code>--set-block-time</code> when mining the first block in a new signet:

<pre>
$ ADDR=$(./bitcoin-cli -datadir=$datadir getnewaddress); ../contrib/signet/miner --cli="./bitcoin-cli -datadir=$datadir" generate --address $ADDR --grind-cmd="./bitcoin-util grind" --nbits=$NBITS --set-block-time=$(date +%s)
</pre>

This will create an address, and then mine the first block to that address. (Note that you may need to create a wallet first.)

To keep the mining ongoing from there, aiming for blocks arriving every 10 minutes on average, we can run:

<pre>
$ ../contrib/signet/miner --cli="./bitcoin-cli -datadir=$datadir" generate --address $ADDR --grind-cmd="./bitcoin-util grind" --nbits=$NBITS --ongoing
</pre>

Next is to have your friends/colleagues/etc join the network by setting the <code>signetchallenge</code> to the same as above, and connecting to your node.

===Example Script===

A full example script can be found at https://en.bitcoin.it/wiki/Signet:Custom:Script

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Testnet

2020-12-03T13:56:08Z

Wiz: /* Block explorers */

The '''testnet''' is an alternative Bitcoin [[block chain]], to be used for testing. Testnet coins are separate and distinct from actual bitcoins, and are never supposed to have any value. This allows application developers or bitcoin testers to experiment, without having to use real bitcoins or worrying about breaking the main bitcoin chain.

Run bitcoin-qt or bitcoind with the -testnet flag to use the testnet (or put testnet=1 in the bitcoin.conf file).

There have been three generations of testnet. Testnet2 was just the first testnet reset with a different genesis block, because people were starting to trade testnet coins for real money. '''Testnet3''' is the current test network. It was introduced with the 0.7 release, introduced a third genesis block, a new rule to avoid the "difficulty was too high, is now too low, and transactions take too long to verify" problem, and contains blocks with edge-case transactions designed to test implementation compatibility. On the December 21 of 2015 SegNet was deployed, to test the Wuille's Segregated Witness proposal.

==Differences==
* Default Bitcoin network protocol listen port is 18333 (instead of 8333)
* Default RPC connection port is 18332 (instead of 8332)
* Bootstrapping uses different DNS seeds.
* A different value of ADDRESSVERSION field ensures no testnet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are 0x0B110907 (instead of 0xF9BEB4D9)
* Minimum [[difficulty]] of 1.0 on testnet is equal to difficulty of 0.5 on mainnet. This means that the mainnet-equivalent of any testnet difficulty is half the testnet difficulty. In addition, if no block has been found in 20 minutes, the difficulty automatically resets back to the minimum for a single block, after which it returns to its previous value.
* A new genesis block
* The IsStandard() check is disabled so that non-standard transactions can be experimented with.

==Genesis Block==

Testnet uses a different genesis block to the main network. You can find it [https://www.biteasy.com/testnet/blocks/000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943 here] or [http://blockexplorer.com/testnet/b/0 here].
The testnet was [https://github.com/gavinandresen/bitcoin-git/commit/feeb761ba07af74a7cd78b8c8f7c2a961fd9ea1c reset with a new genesis block] for the 0.7 bitcoin release.

==Size==
Testnet receives less transactions than the main block chain and is typically much smaller in size. As of January 2018 the size of the data on disk was 14GB, containing data for about 6 years worth of testnet activity. Downloading this data required about 12GB of network activity peaking at 2MB/s rate of transfer.

==External links==

* [https://bitcointalk.org/?topic=4483.0 Testnet in a box forum topic]
* [https://sourceforge.net/projects/bitcoin/files/Bitcoin/testnet-in-a-box/ Testnet-In-A-Box self-contained testnet]
* [https://github.com/freewil/bitcoin-testnet-box Forked/Updated testnet-box]

===Wallets===

Online testnet wallets to help you test your application.

* [http://testnetwallet.com/ TestnetWallet.com]
* [https://CoPay.io/ CoPay.io] wallet supports TestNet accounts

===Faucets===

Once you're done with your test coins, it is a nice gesture to send them back to the faucets, so they become available to other developers.
* [http://tbtc.bitaps.com bitaps.com Testnet Faucet + double spend test tool]
* [http://bitcoinfaucet.uo1.net/ UO1 Testnet Faucet]
* [https://play.google.com/store/apps/details?id=com.mycelium.testnetwallet Mycelium Testnet Wallet for Android with integrated Testnet "faucet" function (Local Trader)]
* [https://testnet-faucet.mempool.co mempool.co testnet3 Faucet]
* [http://kuttler.eu/bitcoin/btc/faucet/ nkuttler's Bitcoin Testnet Faucet]

Offline (2018-09-06):

* [http://tpfaucet.appspot.com/ TP's TestNet Faucet]
* [https://testnet.manu.backend.hamburg/faucet flyingkiwi's TestNet Faucet]

Offline (2016-08-07):

* [http://faucet.luis.im/ luis.im Mojocoin Testnet3 Faucet]
* [https://accounts.blockcypher.com/testnet-faucet BlockCypher Testnet Faucet], also provided as a [http://dev.blockcypher.com/#faucets Testnet faucet API] for test automation

===Block explorers===
* [https://mempool.space/testnet Bitcoin Testnet on mempool.space]
* [http://tbtc.bitaps.com/ Bitcoin Testnet Explorer on bitaps.com]
* [https://www.biteasy.com/testnet/blocks Biteasy.com Testnet Blockexplorer]
* [http://testnet.blockchain.info Blockchain.info Testnet Explorer]
* [http://tbtc.blockr.io/ Bitcoin Testnet on Blockr.io]
* [https://test-insight.bitpay.com/ Bitcoin Testnet on insight.bitpay.com]
* [https://www.blocktrail.com/tBTC BlockTrail Testnet Explorer, Testnet API and Testnet Faucet]
* [https://live.blockcypher.com/btc-testnet/ BlockCypher Testnet Explorer]
[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Bech32 adoption

2020-11-25T16:05:03Z

Wiz: /* Exchanges */

[[Bech32]] is a new bitcoin [[address]] format specified by [[BIP 0173]]. This page tracks the adoption of [[Bech32]].

Ideally wallets and services would first support ''sending to'' bech32 addresses. After almost everything can send to, then people may be willing to adopt bech32 widely for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Bitcoin Core || {{Yes}} || {{Yes}} ||
|-
| Bitcoin Knots || {{Yes}} || {{Yes}} ||
|-
| bcoin || {{Yes}} || {{Yes}} ||
|-
| Electrum || {{Yes}} || {{Yes}} ||
|-
| Armory || {{Yes}} || {{No}} ||
|-
| JoinMarket || {{Yes}} || {{No}} ||
|-
| GreenAddress || {{Yes}} || {{Yes}} ||
|-
| Breadwallet || {{Yes}} || {{No}} || https://twitter.com/udiWertheimer/status/975810157941796864
|-
| Samourai Wallet || {{Yes}} || {{Yes}} ||
|-
| Coinomi || {{Yes}} || {{Yes}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| BTC.com || {{Yes}} || {{No}} ||
|-
| Casa || {{Yes}} || {{No}} ||
|-
| Mycelium || {{Yes}} || {{Yes}} ||
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} ||
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} ||
|-
| Trust Wallet || {{Yes}} || {{Yes}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
| Guarda Wallet || {{Yes}} || {{No}} || [https://twitter.com/GuardaWallet/status/1194270398730448896 twitter announcement]
|-
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Trezor web wallet || {{Acceptable|PR Merged}} || {{No}} ||
|-
| Ledger Live (desktop app) || {{Yes}} || {{Yes}} ||
|-
| KeepKey chrome app || {{No}} || {{No}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} ||
|-
| Ballet + app|| {{Yes}} || {{Yes}} ||
|}

=== Web Wallets ===

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} ||
|-
| BitGo || {{Yes}} || {{Yes}} || Full support on v2 platform, no plans to add support on v1 platform. Also see: https://blog.bitgo.com/native-segwit-addresses-via-bitgos-api-4946f2007be9
|-
| blockchain.info web|| {{Yes}} || {{No}} || https://twitter.com/provoost/status/1037802325874761728
|-
| HolyTransaction || {{Yes}} || {{No}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || open source JavaScript implementation
|-
| Guarda Wallet || {{Yes}} || {{No}} || https://twitter.com/GuardaWallet/status/1194270398730448896
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || https://1fox.com/?c=en/content/blog&id=12
|-
| [[AgoraDesk]] || {{Yes}} || {{No}} ||
|-
| Anycoin Direct || {{Yes}} || {{No}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| BitBargain.co.uk || {{Yes}} || {{No}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || https://bitcoinblog.de/2018/08/10/bitcoin-de-aktiviert-segwit-kunden-sparen-gebuehren/
|-
| Bitfinex || {{Yes}} || {{No}} || https://twitter.com/bitfinex/status/1189164144789983234
|-
| BitMEX || {{yes}} || {{No}} || https://blog.bitmex.com/bitmex-enables-bech32-sending-support/
|-
| Bittrex || {{No}} || {{No}} || https://www.reddit.com/r/Bitcoin/comments/gqt1m6/bittrex_does_not_even_support_withdrawals_to/
|-
| Bittylicious || {{Yes}} || {{No}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{Yes}} || {{Yes}} || https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
|-
| Bitso || {{Yes}} || {{No}} || https://twitter.com/Bitso/status/1203784055340314624?s=20
|-
| Bitwage || {{Evaluating|??}} || {{No}} ||
|-
| Bisq || {{Yes}} || {{Yes}} || As of v1.5.0 https://bisq.network/blog/bisq-v1.5.0-highlights/
|-
| Coinbase.com || {{Yes}} || {{No}} || https://twitter.com/diogorsergio/status/983052769262292992 (Note that Coinbase commerce does not support sending to bech32)
|-
| CoinFalcon || {{Yes}} || {{No}} ||
|-
| Coinfloor || {{Yes}} || {{No}} || https://coinfloor.co.uk/hodl/2020/09/16/a-few-updates-from-coinfloor/
|-
| Coinsbank.com || {{Yes}} || {{Yes}} ||
|-
| Flyp.me || {{Yes}} || {{No}} ||
|-
| GDax || {{Yes}} || {{No}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} ||
|-
| Globitex || {{No}} || {{No}} ||
|-
| HitBTC || {{Yes}} || {{No}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Independent Reserve|| {{Yes}} || {{No}} || https://www.independentreserve.com/bitcoin/investing
|-
| Itbit || {{Evaluating|??}} || {{No}} ||
|-
| Kraken || {{Yes}} || {{No}} || https://twitter.com/krakenfx/status/1060306827848470528
|-
| LedgerX || {{No}} || {{No}} ||
|-
| Liberalcoins || {{Yes}} || {{Yes}} || https://liberalcoins.com
|-
| [[LocalBitcoins]] || {{Yes}} || {{No}} || https://twitter.com/LocalBitcoins/status/1322194709159301120
|-
| Paxful.com || {{Evaluating|??}} || {{No}} ||
|-
| Poloniex.com || {{Yes}} || {{No}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || https://twitter.com/TheRockTrading/status/976787499648512003
|-
| Walltime || {{Yes}} || {{Yes}} || https://walltime.info
|-
| Purse.io || {{Yes}} || {{Yes}} ||
|-
| www.bitwala.com || {{Yes}} || {{Yes}} ||
|-
| Xapo || {{Yes}} || {{No}} ||
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| GenesisCoin || {{No}} || {{No}} ||
|-
| General Bytes || {{Yes}} || {{Yes}} || Depending on configuration. Since version 20190613 https://www.generalbytes.com/en/support/changelog
|-
| Lamassu Douro || {{Yes}} || {{No}} || https://medium.com/@LamassuSupport/announcing-crafty-chnemu-v7-3-9522fe2868
|}

=== Blockchain Explorers ===

For trying these out you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code>. And addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display !! Index !! Notes
|-
| Apirone.com || {{Yes}} || {{Yes}} || https://apirone.com
|-
| bitaps.com || {{Yes}} || {{Yes}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp/
|-
| Bitupper Explorer || {{Yes}} || {{Yes}} || https://bitupper.com/en/explorer/bitcoin
|-
| blockchain.info || {{Yes}} || {{No}} ||
|-
| Blockchair || {{Yes}} || {{Yes}} || https://blockchair.com/
|-
| Blockcypher || {{Yes}} || {{Yes}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || https://blockpath.com
|-
| BTC.com || {{Yes}} || {{Yes}} || https://BTC.com
|-
| Esplora || {{Yes}} || {{Yes}} || Open source explorer, instances are https://blockstream.info/ and https://www.localbitcoinschain.com/
|-
| chaindex || {{Yes}} || {{Yes}} || https://chaindex.com/blockchain/
|-
| Insight || {{No}} || {{No}} || Open source explorer, instances include https://insight.bitpay.com/
|-
| OXT || {{Yes}} || {{Yes}} || https://oxt.me/
|-
| Tradeblock || {{No}} || {{No}} || https://tradeblock.com/bitcoin
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! Invoice addresses !! Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || Payment notifications, merchant dashboard, plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} ||
|-
| [https://cryptochill.com CryptoChill] || {{Yes}} || {{Yes}} || Highly customizable Bitcoin and Lightning Network payment gateway. Multi-sig, HD wallets, API, SDK.
|}

=== Mining Pools ===

{| class="wikitable sortable"
|-
! Name !! Payout !! Notes
|-
| [https://pool.btc.com/ BTC.com Pool] || {{No}} ||
|-
| [http://ckpool.org/ Ckpool] || {{Yes}} ||
|-
| [https://kano.is/ KanoPool] || {{Yes}} || [https://bitcointalk.org/index.php?topic=789369.msg53374508#msg53374508 bitcointalk source]
|-
| [http://poolin.com/ Poolin] || {{Yes}} || [https://bitcointalk.org/index.php?topic=5169994.msg52184844#msg52184844 bitcointalk source]
|-
| [https://slushpool.com/ Slush Pool] || {{Yes}} ||
|-
| [https://ukrpool.com/ Ukr Pool] || {{Yes}} || [https://bitcointalk.org/index.php?topic=5124825.msg51358033#msg51358033 bitcointalk source]
|-
| [https://pool.viabtc.com/ ViaBTC Pool] || {{No}} ||
|}



=== References ===

[[Category:Software]]

Block chain browser

2020-09-10T09:19:29Z

Wiz: /* List of blockchain explorers */

==Block Explorer==

A Blockchain Explorer is a web application to view and query [https://en.bitcoin.it/wiki/Block blocks] <ref>Blockchain for dummies p 99 - Tiana Laurence - ISBN 978-1119365594</ref> working as a [https://en.bitcoin.it/wiki/Web_browser web browser] that is not connected to the internet, like Google Chrome, but to the [https://en.bitcoin.it/wiki/Blockchain Blockchain]. Their primary function is to allow everyone with an internet connection to track in real-time all the [https://en.bitcoin.it/wiki/Transaction_confirmation transactions] or interactions made by each [https://en.bitcoin.it/wiki/Cryptocurrency cryptocurrencies] holders, regardless of his or her level of knowledge and expertise. <ref>Blockchain Enabled Application p.21 - David Metcalf - ISBN 978-1484230800</ref>. However, although there are plenty of Explorer available, only a tiny minority are able to show the transaction using [https://en.bitcoin.it/wiki/Segregated_Witness SegWit] (Bitcoin bech32 addresses start with “bc1”) <ref>Blockchain: A Practical Guide to Developing Business, Law, and Technology Solutions 1st Edition p.19- Joseph J. Bambara - ISBN 978-1260115871</ref>

==The default view==

The default view in the main page generally provides in real time information about of all the last blocks that are being added to the blockchain, most often separated into six columns with this following informations:

'''Block height:''' <ref>Mastering Bitcoin p.28 - Andreas M. Antonopoulos - ISBN 978-1491954386</ref> block number since the Bitcoin [https://en.bitcoin.it/wiki/Genesis_block genesis block] was [https://en.bitcoin.it/wiki/Mining mined]. Each new mined block assumes an increase of one at the height of the block. Thus, the number 492800 in this column means this is the 492800th block mined in the whole history.

'''Age:''' the moment when the block was accepted by a miner and not when the user initiated a payment or transfer to another wallet.

'''[https://en.bitcoin.it/wiki/Transaction_confirmation Confirmation]:''' The most relevant information visible at a glance, the transaction status. If a transaction is «unconfirmed» or «pending», that means the transaction is in the Blockchain, but has not included in a block yet. In average, it takes typically 10 minutes for a bitcoin transaction to be confirmed. It will take about one hour to get «confirmed» by six confirmations.

'''Transaction list (TX):''' number of transactions included in the block. <ref>Blockchain: A Practical Guide to Developing Business, Law, and Technology Solutions 1st Edition p.18- Joseph J. Bambara - ISBN 978-1260115871</ref>

'''Reward:''' the reward for those (miners) who mined the block.

'''Mined by:''' name of the miner who mined this block. Usually a pool of miners who had been involved in.

'''Size:''' size of the transaction obtained by adding the sizes of each transactions included in the block. This data is always provided in bytes.

==The browser==

In the same way as with an Internet browser, the user needs to enter a request to begin his search. It can be a transaction hash or TXID <ref>beginning-blockchain-guide-building-solutions p.278 - Bikramaditya Singhal - ISBN 978-1484234433</ref>(sequence of 64 characters hexadecimal (0 to 9 and a to f) numbers used to uniquely identify a particular transaction) or a block height for example. Automatically, a page containing all the details about the transaction is loaded according to the request. Advanced information contains all the movements in this transaction and is only available at the user's request. Most of the time, a bitcoin transaction has several input and output [https://en.bitcoin.it/wiki/Bitcoin_address addresses] insofar as it allows a sender to save time and money by sending to several addresses at once. All the following data will be displayed:

'''TXID:''' as mentioned above

'''Input:''' transaction inputs are pointers to UTXO <ref>Blockchain Enabled Application p.18 - David Metcalf - ISBN 978-1484230800</ref>. They point to a specific UTXO by reference to the transaction hash and sequence number where the UTXO is recorded in the blockchain.

'''Output:''' contains instructions for sending bitcoins <ref>Blockchain Enabled Application p.18 - David Metcalf - ISBN 978-1484230800</ref>.

'''Value:''' the number of Satoshi (1 BTC = 100,000,000 Satoshi) that this output will be worth when claimed.

'''ScriptPubKey:''' the second half of a script. There can be more than one output. Because each output from one transaction can only ever be referenced once by an input of a subsequent transaction, the entire combined input value needs to be sent in an output if the user doesn't want to lose it. <ref>beginning-blockchain-guide-building-solutions p.201-202 - Bikramaditya Singhal - ISBN 978-1484234433</ref> If the input is worth 50 BTC but a consumer only want to send 25 BTC, Bitcoin will create two outputs worth 25 BTC. This section is divided into two parts. The first, the top line, showing the total amount that the recipient has to receive in BTC, known as the destination. And the other part, below, showing the amount of bitcoins back to the user that remains in the wallet and which can be used as a new input in a subsequent transaction. Any input bitcoins not redeemed in an output is considered a transaction fee.

'''Transaction Fees:''' most transactions include transaction fees, which compensate the bitcoin miners for securing the network. Transaction fees serve as an incentive to include (mine) a transaction into the next block and also as a disincentive against “spam” transactions or any kind of abuse of the system, by imposing a small cost on every transaction. Transaction fees are collected by the miner who mines the block that records the transaction on the blockchain. <ref>Mastering Bitcoin p.127 - Andreas M. Antonopoulos - ISBN 978-1491954386</ref>

'''Coinbase Data:''' This field must be between 2 and 100 bytes. Except for the first few bytes the rest of the coinbase data can be used by miners in any way they want; it is arbitrary data. In the genesis block, for example, Satoshi Nakamoto added the text “The Times 03/Jan/ 2009 Chancellor on brink of second bailout for banks” in the coinbase data, using it as a proof of the date and to convey a message. Currently, miners use the coinbase data to include extra nonce values and strings identifying the mining pool. <ref>Mastering Bitcoin p.225 - Andreas M. Antonopoulos - ISBN 978-1491954386</ref>

==List of blockchain explorers==
* https://mempool.space Open-source Bitcoin Explorer
* https://bitaps.com Explorer that supports Segwit
* https://apirone.com/btc/ Explorer that supports Segwit
* https://blockstream.info/
* https://bitupper.com/en/explorer/bitcoin Explorer that supports Segwit
* http://btcblockexplorer.financialplugins.com
* https://bitcoinchain.com
* https://bitinfocharts.com/bitcoin
* https://blockchain.info
* https://blockchair.com/ Explorer that supports Segwit, privacy centric
* https://blockexplorer.com/
* https://btc.com/ Explorer that supports Segwit
* https://chain.so/BTC
* https://chainz.cryptoid.info/btc Explorer that supports Segwit
* https://explorer.bitcoin.com/btc
* https://insight.bitpay.com
* https://live.blockcypher.com/btc
* https://multihash.net
* https://btc.blockdozer.com
* https://www.blockonomics.co Explorer that supports Segwit
* https://www.blocktrail.com/BTC
* https://www.smartbit.com.au
* https://explorer.poolin.com/ Explorer that supports Segwit

==References==
<references />