Fetch Payload Bodies

Fetch execution payload bodies by execution block hash.

Use engine payload-bodies to call engine_getPayloadBodiesByHashV1 for one or more execution block hashes.

The command prints body availability plus transaction and withdrawal counts. The transactions returned by this Engine API method are raw transaction bytes, so Rex summarizes them instead of rendering a full transaction table.

Command

First get an execution block hash with Block:

rex chain block --block latest

Then query the authenticated Engine API:

rex engine \
  --jwt-secret ./jwt.hex \
  payload-bodies \
  --hash 0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Repeat --hash to request multiple bodies in one call:

rex engine \
  --jwt-secret ./jwt.hex \
  payload-bodies \
  --hash 0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa \
  --hash 0xbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb

Example Output

ENGINE PAYLOAD BODIES

Requested:    2
Found:        2
Transactions: 184
Withdrawals:  16

BLOCK HASH                                                         FOUND       TXS  WITHDRAWALS
0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa     yes          91            8
0xbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb yes          93            8

Field Notes

• FOUND is no when the execution client returns null for a requested body.
• TXS counts raw transaction byte entries, not decoded transaction hashes.
• WITHDRAWALS is - when the body predates withdrawals or the node returns no withdrawal field.

Use the execution block hash from the execution payload. Do not pass a beacon block root; those are consensus-layer identifiers and do not identify execution payload bodies.