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

0x89e0daa4...9c862929

From

0xaa7b2b66...c28303e4

Block

275058

Status

Success

Overview

Update ID

1220825c30...4adfc649

Offset

956275

Record Time

Aug 5, 2026, 21:46:41 UTC

Command ID

841f4559d19b...59b2720a

Synchronizer ID

da::1220d56d...ad0f65eb

Events (2)

exercised77e0a44b32dbf894220a7edd0513333948973d4eb6e95b148b1897d8526f526a:Zenith.Evm.Rules:BlockProposal

Contract:00893fa098...1416c1f5

Choice: BlockProposal_AddTransactions

Payload

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

created

Payload

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