> For the complete documentation index, see [llms.txt](https://docs.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsvblockchain.org/broadcasting/web-broadcasters.md).

# Web Broadcasters

Paste a raw transaction into a web form and send it. No code, no account.

Two block explorers offer a web page where you paste a hex-encoded transaction and submit it with a button. Nothing to install and nothing to authenticate. They are the quickest way to push a single transaction when you already have the hex, and a convenient way to check whether a transaction your application failed to send is actually valid.

| Service      | Mainnet                                                          | Testnet                                                                    |
| ------------ | ---------------------------------------------------------------- | -------------------------------------------------------------------------- |
| WhatsOnChain | [whatsonchain.com/broadcast](https://whatsonchain.com/broadcast) | [test.whatsonchain.com/broadcast](https://test.whatsonchain.com/broadcast) |
| Bitails      | [bitails.io/broadcast](https://bitails.io/broadcast)             | [test.bitails.io/broadcast](https://test.bitails.io/broadcast)             |

## How to use them

1. Serialise the signed transaction to hex. With the TypeScript SDK that is `tx.toHex()`; with Go, `hex.EncodeToString(tx.Bytes())`; with Python, `tx.hex()`. The SV Node RPC `signrawtransaction` also returns hex.
2. Open the broadcast page for the network the transaction belongs to.
3. Paste the hex and submit.
4. On success the page shows the transaction ID and links to the explorer's transaction view. On failure it shows the node's rejection reason, for example `mempool conflict`, `insufficient priority`, or `mandatory-script-verify-flag-failed`.

The pages accept only the plain raw format. If you have an Extended Format or BEEF serialisation, convert it to raw first; the SDKs do this with `tx.toHex()` regardless of how the transaction was loaded.

## When they are the right tool

* **One-off sends.** Moving funds from a paper key, consolidating a few outputs, or publishing a single data transaction.
* **Debugging.** If your application's broadcast fails, pasting the same hex here tells you in seconds whether the transaction is the problem or your integration is.
* **Support.** A user can send you a transaction they could not broadcast and you can push it for them without touching your production systems.
* **Learning.** The explorer immediately shows the decoded transaction, so you can see inputs, outputs, and scripts as the network sees them.

## When they are not

* Anything automated. Use [Arcade](/broadcasting/arcade.md) or an [API broadcaster](/broadcasting/api-broadcasters.md).
* Transactions that spend unconfirmed outputs of transactions you have not broadcast yet. Send the parents first, in order.
* Very large transactions. Browser forms have practical limits well below what the network accepts. Use Bitails's multipart API or Arcade's binary endpoint instead.

Both explorers relay to their own nodes and from there into the mining network. Neither gives you a status feed; refresh the explorer's transaction page or query its API to see when the transaction is mined.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bsvblockchain.org/broadcasting/web-broadcasters.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.