Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #120115
Committed on Canton
Participant commits update 1220372a51…d7bcd8Imported to the execution layers
Importer applies block #120115 from GatewayHeadStep 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.
Total
—
Block → Canton commit
—
Step durations aren't available on this connection, so timings are shown as “—” rather than a misleading 0ms. The stages did occur (the Canton↔EVM correlation is confirmed) — only the sub-step wall-clock timing is unavailable, as the sequencer reports the steps as a single atomic commit.
0xf8ae820ced8405f5e1008301d4c0940af70fb293003422fb174e4ad03787337903128b80b844a9059cbb00000000000000000000000020b02f4ddf17cc84c4fe5920b92b242304f84d8400000000000000000000000000000000000000000000000340aad21b3b700000831c946ea026900b01ddf78c11195b6c6e316475fb90fc95e153802d0520b8347712476afaa0277f1066eeda0454ceff3ff4bcca693024e638c87e43e7db294770c048f3950b