> 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/api-reference/transaction-types/plaintext-tx.md).

# PlaintextTx

Unencrypted transaction view for debugging

Unencrypted transaction view returned by debug writes (`.dwrite`). Contains the same fields as a shielded transaction but with **plaintext** calldata (before AES-GCM encryption).

## Definition

```python
@dataclass(frozen=True)
class PlaintextTx:
    to: ChecksumAddress | None
    data: HexBytes
    nonce: int
    gas: int
    gas_price: int
    value: int
    gas_payment: GasPayment = field(default_factory=GasPayment.auto)
```

## Fields

| Field         | Type                                                                           | Description                                                 |
| ------------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------- |
| `to`          | `ChecksumAddress \| None`                                                      | Recipient address, or `None` for contract creation          |
| `data`        | `HexBytes`                                                                     | **Plaintext** calldata (before encryption)                  |
| `nonce`       | `int`                                                                          | Sender's transaction count                                  |
| `gas`         | `int`                                                                          | Gas limit                                                   |
| `gas_price`   | `int`                                                                          | Gas price in wei                                            |
| `value`       | `int`                                                                          | Amount of wei to transfer                                   |
| `gas_payment` | [`GasPayment`](/clients/python/api-reference/transaction-types/gas-payment.md) | Resolved public fee choice, matching the signed transaction |

## Example

```python
result = await contract.dwrite.transfer(recipient, 1000)

plaintext = result.plaintext_tx
print(f"To: {plaintext.to}")
print(f"Plaintext data: {plaintext.data.to_0x_hex()}")
print(f"Gas: {plaintext.gas}")
```

## Notes

* The `data` field is unencrypted — contrast with [`UnsignedSeismicTx.data`](/clients/python/api-reference/transaction-types/unsigned-seismic-tx.md) which holds ciphertext
* Only available via `.dwrite`, not `.write`
* The broadcast transaction uses the encrypted data, not this plaintext

## See Also

* [DebugWriteResult](/clients/python/api-reference/transaction-types/debug-write-result.md) — contains PlaintextTx
* [UnsignedSeismicTx](/clients/python/api-reference/transaction-types/unsigned-seismic-tx.md) — shielded version with encrypted data


---

# 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/api-reference/transaction-types/plaintext-tx.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.