Track Transactions

Check a SubmissionCopy Anchor Link

Use the ID returned by execution execute, not a transaction or UserOp hash:

namera execution status 0199dfe1-0000-7000-8000-000000000003

-> Status: Pending confirmation
-> UserOp Hash: 0x1111111111111111111111111111111111111111111111111111111111111111

Not confirmed yet. Check again with:
  namera execution status 0199dfe1-0000-7000-8000-000000000003

The command checks once. Repeat this read until it reaches Confirmed or Failed. Queued and Pending confirmation are not terminal states.

Save Machine-Readable StatusCopy Anchor Link

namera --output json execution status 0199dfe1-0000-7000-8000-000000000003

{
  "namespace": "eip155",
  "submissionId": "0199dfe1-0000-7000-8000-000000000003",
  "status": "submitted",
  "userOperationHash": "0x1111111111111111111111111111111111111111111111111111111111111111"
}

A confirmed response includes the full execution record. A failed response contains its submission ID and status, without an invented failure reason. See execution status for the state list.

Read Confirmed HistoryCopy Anchor Link

namera execution list

Found 1 confirmed execution:

-> Account: 👛 Example account
-> Transaction Hash: 0x5555555555555555555555555555555555555555555555555555555555555555
-> UserOp Hash: 0x1111111111111111111111111111111111111111111111111111111111111111
-> Network: Base Sepolia
-> Actor: Example integration (API Key)
-> Session key: Example session

Use JSON to obtain items and nextCursor. When the cursor is not null, pass it to --cursor on the next read.

History contains confirmed executions only. It is not a list of pending submissions. If a result was lost, follow Handle Retries and Recovery.

Example output uses fixture accounts and hashes, captured with the CLI's output formatters. Plain-text output is shown without terminal colors; your values and relative expiry dates will differ.