> For the complete documentation index, see [llms.txt](https://docs.seismic.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seismic.systems/clients/python/namespaces/methods/debug-send-shielded-transaction.md).

# debug\_send\_shielded\_transaction

Send shielded transaction and return debug artifacts

Same send pipeline as `send_shielded_transaction`, plus plaintext/encrypted transaction views.

## Signatures

```python
# sync
w3.seismic.debug_send_shielded_transaction(...same args as send_shielded_transaction...) -> DebugWriteResult

# async
await w3.seismic.debug_send_shielded_transaction(...same args...) -> DebugWriteResult
```

## Returns

[`DebugWriteResult`](/clients/python/api-reference/transaction-types/debug-write-result.md) with:

| Field          | Type                                                                                          | Description                                  |
| -------------- | --------------------------------------------------------------------------------------------- | -------------------------------------------- |
| `tx_hash`      | `HexBytes`                                                                                    | Transaction hash from the network            |
| `plaintext_tx` | [`PlaintextTx`](/clients/python/api-reference/transaction-types/plaintext-tx.md)              | Transaction with **unencrypted** calldata    |
| `shielded_tx`  | [`UnsignedSeismicTx`](/clients/python/api-reference/transaction-types/unsigned-seismic-tx.md) | Full `TxSeismic` with **encrypted** calldata |

The transaction **is** broadcast — this is not a dry run.

The optional top-level `gas_payment` keyword defaults to Auto before signing. Both transaction views include the resolved `GasPayment`, and the separate signed estimate uses that same choice. See [GasPayment](/clients/python/api-reference/transaction-types/gas-payment.md) for token selection and compatibility.

## Example

```python
result = w3.seismic.debug_send_shielded_transaction(to="0xTarget", data=calldata)
print(result.tx_hash.hex())
print(result.plaintext_tx.data.hex())
print(result.shielded_tx.data.hex())
```

## Notes

* Parameters are identical to [`send_shielded_transaction`](/clients/python/namespaces/methods/send-shielded-transaction.md)
* For contract interactions, prefer `contract.dwrite.functionName(...)` which handles ABI encoding automatically
* Be careful logging `plaintext_tx` in production — it contains unencrypted calldata

## See Also

* [send\_shielded\_transaction](/clients/python/namespaces/methods/send-shielded-transaction.md) — Same pipeline without debug info
* [contract.dwrite](/clients/python/contract/namespaces/dwrite.md) — High-level debug write API
* [DebugWriteResult](/clients/python/api-reference/transaction-types/debug-write-result.md) — Return type reference


---

# 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.seismic.systems/clients/python/namespaces/methods/debug-send-shielded-transaction.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.