Step durations aren't available on this connection, so per-step and total timings are omitted rather than shown as a misleading 0ms. The lifecycle stages above did occur (the Canton↔EVM correlation is confirmed); only the sub-step wall-clock timing is unavailable — it requires a data source that reports distinct step timestamps rather than an atomic commit.

Resulting EVM Transaction

EVM Tx Hash

0xd4eb37ae...4ae1c9f8

From

0xaa7b2b66...c28303e4

Block

191067

Status

Success

Overview

Update ID

1220c85ebc...63e27192

Offset

656949

Record Time

Jul 31, 2026, 16:00:37 UTC

Command ID

1112ff38995b...667e13cc

Synchronizer ID

da::1220d56d...ad0f65eb

Events (2)

exercised77e0a44b32dbf894220a7edd0513333948973d4eb6e95b148b1897d8526f526a:Zenith.Evm.Rules:BlockProposal

Contract:009140f190...dbb846b1

Choice: BlockProposal_AddTransactions

Payload

{ "newTransactions": [ "02f86b830e4a258217ac01843b9aca0082520894aa7b2b66b8c6c6a792fdd75e6a6467b1c28303e48080c001a01d5a763a24bceb77af4066241b540ca5a2091501e547cb07da2d3d9d623525f9a049b21716fbfe82066dfc58caf4d74a93a6f7ce88b67ea9c20b84636c739d0ec4" ], "source": "Validator1::12207a8e828b3131791dde7f3405203e3913e23c096c30e25f8263489d05ce4c12bf" }

created

Payload

{ "chainId": { "zeo": "zeo::1220789efd2002a6854a5c2b15b4b7fadafe10b4d1fb96b5216283b364d0421379e0", "version": "" }, "proposer": "Validator1::12207a8e828b3131791dde7f3405203e3913e23c096c30e25f8263489d05ce4c12bf", "transactions": [ "02f86b830e4a258217ac01843b9aca0082520894aa7b2b66b8c6c6a792fdd75e6a6467b1c28303e48080c001a01d5a763a24bceb77af4066241b540ca5a2091501e547cb07da2d3d9d623525f9a049b21716fbfe82066dfc58caf4d74a93a6f7ce88b67ea9c20b84636c739d0ec4" ], "withdrawals": [], "observers": { "map": [ [ "Validator1::12207a8e828b3131791dde7f3405203e3913e23c096c30e25f8263489d05ce4c12bf", {} ] ] } }