BitRef Bitcoin Explorer Endpoints

BitRef.com provides a set of URL endpoints for exploring and viewing data from the Bitcoin blockchain.

The endpoints allow you to link directly to Bitcoin addresses, public keys, transactions, transaction inputs and outputs, blocks, and the BitRef Bitcoin transaction accelerator.

The URLs are designed to be human-readable and can be used directly in websites, applications, exchanges, mining pools, payment systems, monitoring tools, and other services that need to link users to specific Bitcoin blockchain data.

Addresses

URL

https://bitref.com/{ADDRESS}

Example

https://bitref.com/bc1quy5nvh8npg0qdpnk35wctey8e923yms9udzfjr

Displays information about a specific Bitcoin address.

BitRef supports all commonly used Bitcoin address and output types, including:

• P2PK
• P2PKH
• P2SH
• P2WPKH
• P2WSH
• P2TR
• and other supported Bitcoin script types

The address page displays the current balance and transaction history associated with the address.

The balance is separated into confirmed and unconfirmed amounts.

The transaction history provides detailed information about the transactions associated with the address, including confirmation status, date and time, fee information, amounts, and their corresponding USD values.

For each transaction, BitRef provides both the current USD value and, where applicable, the historical USD value at the time of the transaction.

The transaction details contain additional blockchain information and can be opened directly from the address page.

Public Keys

URL

https://bitref.com/{PUBLIC_KEY}

Example

https://bitref.com/02ea0cf4d6d151d0528b07efa79cc7403d77cb9195e2e6c8374f5074b9a787e287

BitRef supports direct lookup of Bitcoin public keys for historical and compatibility reasons.

Both compressed and uncompressed public keys are supported.

The public-key page displays the balance and transactions associated with the public key, in a similar way to an address page.

Public keys are not converted to addresses

BitRef treats a public key as a separate Bitcoin identifier.

Some Bitcoin explorers convert or hash a public key into an address representation, such as a P2PKH address, and then display the activity associated with that address.

BitRef does not do this.

A public-key output, such as a historical P2PK output, is a different Bitcoin script from a P2PKH address. Such outputs do not necessarily have a corresponding Bitcoin address, so BitRef uses the public key itself as the identifier.

This is particularly relevant for historical Bitcoin transactions.

Direct payments to public keys were used more frequently during the early years of Bitcoin. For example, some early mining rewards were paid directly to public keys.

Transactions

Transaction Details

URL

https://bitref.com/tx/{TXID}

Example

https://bitref.com/tx/c803381aae1b606b7b5739148a88ddc4e498c9f161a77243e7b57401ce8d14b3

Displays detailed information about a specific Bitcoin transaction.

The transaction may be either:

• Confirmed — the transaction has been included in a Bitcoin block.
• Unconfirmed — the transaction is currently in the Bitcoin mempool and has not yet been included in a block.

BitRef displays extensive information about the transaction, including its inputs, outputs, amounts, fees, confirmation status, and other relevant blockchain data.

The information available can differ depending on whether the transaction is confirmed or unconfirmed.

The transaction page is also used by the transaction-specific URL fragments described below to highlight individual addresses, inputs, or outputs.

Highlight a Bitcoin Address

URL

https://bitref.com/tx/{TXID}#address:{ADDRESS}

Example

https://bitref.com/tx/c803381aae1b606b7b5739148a88ddc4e498c9f161a77243e7b57401ce8d14b3#address:bc1quy5nvh8npg0qdpnk35wctey8e923yms9udzfjr

Highlights a specific Bitcoin address in the transaction's inputs and outputs.

This is useful when a transaction contains multiple addresses and an application wants to direct a user to a particular address.

Example use case

An exchange may combine many user withdrawals into a single Bitcoin transaction.

Instead of sending every user to the generic transaction URL:

https://bitref.com/tx/{TXID}

the exchange can provide each user with:

https://bitref.com/tx/{TXID}#address:{USER_ADDRESS}

When the user opens the link, their address is highlighted in the transaction, making it immediately clear that the address is one of the transaction recipients and showing the amount associated with it.

This is particularly useful for exchanges, mining pools, payment processors, and other services that create transactions containing multiple payments.

Highlight a Transaction Input

URL

https://bitref.com/tx/{TXID}#input:{INPUT_ID}

Example

https://bitref.com/tx/c803381aae1b606b7b5739148a88ddc4e498c9f161a77243e7b57401ce8d14b3#input:0

Highlights a specific input in a Bitcoin transaction.

INPUT_ID is the zero-based index of the input within the transaction.

For example:

#input:0

selects the first input, while:

#input:1

selects the second input.

This can be useful for exchanges and other services that monitor incoming Bitcoin transactions and need to direct a user or operator to a particular transaction input.

Highlight a Transaction Output

URL

https://bitref.com/tx/{TXID}#output:{OUTPUT_ID}

Example

https://bitref.com/tx/c803381aae1b606b7b5739148a88ddc4e498c9f161a77243e7b57401ce8d14b3#output:0

Highlights a specific output in a Bitcoin transaction.

OUTPUT_ID is the zero-based index of the output within the transaction.

For example:

#output:0

selects the first output.

The transaction page automatically scrolls to the specified output and highlights it.

This is useful when a specific output needs to be identified unambiguously, for example when an exchange wants to direct a user to the exact output representing their withdrawal.

Unlike #address:{ADDRESS}, which identifies an address wherever it appears in the transaction, #output:{OUTPUT_ID} identifies one specific transaction output.

Bitcoin Transaction Accelerator

URL

https://bitref.com/accelerator/#{TXID}

Example

https://bitref.com/accelerator/#c803381aae1b606b7b5739148a88ddc4e498c9f161a77243e7b57401ce8d14b3

BitRef provides a Bitcoin transaction accelerator for unconfirmed transactions.

The accelerator uses the transaction ID (TXID) to retrieve the raw transaction and rebroadcast it through a network of highly connected Bitcoin nodes.

Only the TXID is required.

BitRef automatically retrieves the raw transaction data and rebroadcasts the transaction.

Rebroadcasting can help improve transaction propagation when an unconfirmed transaction has not reached enough nodes or relevant parts of the Bitcoin network.

The accelerator does not guarantee that a transaction will be confirmed within a particular time. Confirmation ultimately depends on the Bitcoin network, transaction fee rate, miner policies, and current mempool conditions.

The accelerator is intended for unconfirmed transactions.

Blocks

URL

https://bitref.com/block/{BLOCK_HEIGHT}

Example

https://bitref.com/block/840000

Displays detailed information about a specific Bitcoin block.

BitRef uses the block height as the URL identifier instead of the block hash.

For example:

https://bitref.com/block/840000

identifies Bitcoin block 840000.

Using the block height makes block URLs shorter, easier to read, remember, and share than URLs containing a 64-character block hash.

The block page provides extensive information about the selected block, including its blockchain metadata and transactions.

URL Fragment Parameters

BitRef transaction URLs support fragments that control which part of a transaction is highlighted when the page is opened.

For example:

https://bitref.com/tx/{TXID}#address:{ADDRESS}

https://bitref.com/tx/{TXID}#input:0

https://bitref.com/tx/{TXID}#output:0

These fragments do not identify a different transaction. They control which part of the transaction is highlighted when the transaction page is opened.

This functionality is particularly useful when integrating BitRef links into exchange, mining pool, payment processor, accounting, and monitoring systems.

Endpoint Summary