Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #48
Committed on Canton
Participant commits update 12209f9916…30959dImported to the execution layers
Importer applies block #48 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.
0x02f865830e4a2506010f82520894000000000000000000000000000000000000dead0180c001a0a54d8643f3e29dbda867097dfde111d67413231e90f11ce1c670b5fe8c1080aea077e7a3bd504c83fdca8e41b6ea7f5802adae4b93a4bdbd9098d46ef914df3490