Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #113887
Committed on Canton
Participant commits update 12202cf847…ef3d16Imported to the execution layers
Importer applies block #113887 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.
0x02f901f4830e4a25820bba830f4240831e8480830c992b94925e8d5ec0b8c417bcadbeae4d7e7f22376003fc80b90184de11ad050000000000000000000000003bd945d969e2a4b76edf8cf09fe6357bb6682f4f00000000000000000000000041f21e381a70e404854d1f95788208bbc6a8cd720000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000453ec8de800000000000000000000000000000000000000000000000000000000050494860000000000000000000000000000000000000000000000000000000000000014000000000000000000000000ac4eaedcb1a003163ed8e83b3959753b0eba845a000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c001a069dc9cca2ff0bf39c681b7ad9650668a5a44fb3f771274ee6a87cce6fe3b4e3ca0714ff3ef4622c5f75c438f2bdca36fc16ea8541f90f6ad84a1b0cef981d31ff3