Transactions

Transactions in an environment are processed by the same rules as the chain they model: nonces, gas limits, base fee, priority fee, and ordering are all honored. The difference is that you control the parameters and can observe everything.

Submitting

Use any standard client against the environment's RPC endpoint, or submit through the API:

POST /v1/environments/env_7f3a2c/execute
{
  "ops": [
    { "type": "tx", "from": "user_1", "to": "0x8c21…9b04", "value": "1 ether" }
  ]
}

Ordering and blocks

By default, operations in a single request execute in order within one block. You can advance blocks explicitly, schedule operations for future blocks, or enable automatic mining on a fixed cadence to mimic live conditions.

Receipts and traces

Every transaction yields a receipt and a full call trace. Traces include each internal call, its input and output, gas consumed, and any revert reason, decoded when the ABI is known.

nome tx trace env_7f3a2c 0x41…8a --decode