> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dfns.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Broadcast

> Network-specific transaction payload references for the Dfns sign and sign-and-broadcast endpoints across all supported blockchains.

A broadcast is sending a transaction to the blockchain network so nodes can receive and include it in the chain.

In these docs "broadcast" refers to submitting a (signed) transaction to the blockchain (the node/rpc) so it's propagated and eventually confirmed. Examples and API calls that "sign an unsigned transaction and broadcast it to chain" are available in the examples pages.

Use broadcast when you want the wallet to sign (using its underlying key) and publish a prepared transaction or PSBT to the blockchain.

The endpoint accepts either a signed/partially-signed PSBT (Bitcoin/Litecoin) or an unsigned transaction payload for many chains; the wallet service will sign (when applicable) and broadcast it to the network. Check out the examples for exact request formats and chain-specific transaction examples.

## Speed up and cancel

If a broadcasted transaction is stuck in the mempool (status `Broadcasted`), you can speed it up or cancel it:

* [Speed Up Transaction](/api-reference/wallets/speed-up-transaction): Rebroadcasts the transaction with higher fees (EVM only)
* [Cancel Transaction](/api-reference/wallets/cancel-transaction): Replaces the transaction with a zero-value self-transfer (EVM only)

<Note>
  Success is not guaranteed. If the original transaction confirms before the replacement is mined, the speed-up or cancel will fail.
</Note>

**What endpoint should I use for my transactions?**

* **Transfer:** call the Transfer Asset endpoint for native tokens, ERC-20/721, SPL, Cardano assets, etc. It creates a wallet transfer request, requires user action signing, supports fee sponsorship, idempotency via externalId, policy approvals, status tracking, and indexing (txHash, dateConfirmed). See [Transfer](/api-reference/transfer).
* **Broadcast (Sign & Broadcast):** use the Broadcast Transaction endpoint when you’ve built a raw/serialized transaction (or need to call arbitrary smart contract functions, mint, deploy contracts). This endpoint signs the transaction with the wallet key and broadcasts it; it also returns request status and txHash. See [Broadcast](/api-reference/broadcast).
* **Sign (Generate Signature):** use Generate Signature only when you need an off-chain signature (no broadcast). Note this wallet endpoint is deprecated in favor of the Keys API; it does not submit anything to the chain.

## Transaction request object