# debug\_send\_shielded\_transaction

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.

## 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: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.seismic.systems/clients/python/namespaces/methods/debug-send-shielded-transaction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.