Canton Ledger Transaction
Op 1: 0xd8b5e7c0...34fb8c96
Relayer Wraps Tx
Eth tx → Canton BlockProposal
Validator2 — Re-execute
participant2 · REVM re-execution
Validator3 — Re-execute
participant3 · REVM re-execution
Illustrative visualization. Canton commits Command → Consensus → Finalization atomically within a single transaction, so individual Canton step durations are estimates. Measured anchors from on-chain timestamps: Canton record time → synchronizer effective time, and effective time → EVM block timestamp (second granularity).
Op 2: 0x4ac046ae...9a2922f1
Relayer Wraps Tx
Eth tx → Canton BlockProposal
Validator2 — Re-execute
participant2 · REVM re-execution
Validator3 — Re-execute
participant3 · REVM re-execution
Illustrative visualization. Canton commits Command → Consensus → Finalization atomically within a single transaction, so individual Canton step durations are estimates. Measured anchors from on-chain timestamps: Canton record time → synchronizer effective time, and effective time → EVM block timestamp (second granularity).
Op 3: 0x4ed5dfdd...cd6b769a
Relayer Wraps Tx
Eth tx → Canton BlockProposal
Validator2 — Re-execute
participant2 · REVM re-execution
Validator3 — Re-execute
participant3 · REVM re-execution
Illustrative visualization. Canton commits Command → Consensus → Finalization atomically within a single transaction, so individual Canton step durations are estimates. Measured anchors from on-chain timestamps: Canton record time → synchronizer effective time, and effective time → EVM block timestamp (second granularity).
Op 4: 0x265a39d8...abbed295
Relayer Wraps Tx
Eth tx → Canton BlockProposal
Validator2 — Re-execute
participant2 · REVM re-execution
Validator3 — Re-execute
participant3 · REVM re-execution
Illustrative visualization. Canton commits Command → Consensus → Finalization atomically within a single transaction, so individual Canton step durations are estimates. Measured anchors from on-chain timestamps: Canton record time → synchronizer effective time, and effective time → EVM block timestamp (second granularity).
Op 5: 0x9fed05ec...c2551181
Relayer Wraps Tx
Eth tx → Canton BlockProposal
Validator2 — Re-execute
participant2 · REVM re-execution
Validator3 — Re-execute
participant3 · REVM re-execution
Illustrative visualization. Canton commits Command → Consensus → Finalization atomically within a single transaction, so individual Canton step durations are estimates. Measured anchors from on-chain timestamps: Canton record time → synchronizer effective time, and effective time → EVM block timestamp (second granularity).
Op 6: 0x0a21fff1...6c840288
Relayer Wraps Tx
Eth tx → Canton BlockProposal
Validator2 — Re-execute
participant2 · REVM re-execution
Validator3 — Re-execute
participant3 · REVM re-execution
Illustrative visualization. Canton commits Command → Consensus → Finalization atomically within a single transaction, so individual Canton step durations are estimates. Measured anchors from on-chain timestamps: Canton record time → synchronizer effective time, and effective time → EVM block timestamp (second granularity).
Op 7: 0x701c0825...97287c47
Relayer Wraps Tx
Eth tx → Canton BlockProposal
Validator2 — Re-execute
participant2 · REVM re-execution
Validator3 — Re-execute
participant3 · REVM re-execution
Illustrative visualization. Canton commits Command → Consensus → Finalization atomically within a single transaction, so individual Canton step durations are estimates. Measured anchors from on-chain timestamps: Canton record time → synchronizer effective time, and effective time → EVM block timestamp (second granularity).
Op 8: 0xcdc282b2...89107542
Relayer Wraps Tx
Eth tx → Canton BlockProposal
Validator2 — Re-execute
participant2 · REVM re-execution
Validator3 — Re-execute
participant3 · REVM re-execution
Illustrative visualization. Canton commits Command → Consensus → Finalization atomically within a single transaction, so individual Canton step durations are estimates. Measured anchors from on-chain timestamps: Canton record time → synchronizer effective time, and effective time → EVM block timestamp (second granularity).
Op 9: 0xa69e243a...2a444ac3
Relayer Wraps Tx
Eth tx → Canton BlockProposal
Validator2 — Re-execute
participant2 · REVM re-execution
Validator3 — Re-execute
participant3 · REVM re-execution
Illustrative visualization. Canton commits Command → Consensus → Finalization atomically within a single transaction, so individual Canton step durations are estimates. Measured anchors from on-chain timestamps: Canton record time → synchronizer effective time, and effective time → EVM block timestamp (second granularity).
Op 10: 0x38f65538...fcfd9976
Relayer Wraps Tx
Eth tx → Canton BlockProposal
Validator2 — Re-execute
participant2 · REVM re-execution
Validator3 — Re-execute
participant3 · REVM re-execution
Illustrative visualization. Canton commits Command → Consensus → Finalization atomically within a single transaction, so individual Canton step durations are estimates. Measured anchors from on-chain timestamps: Canton record time → synchronizer effective time, and effective time → EVM block timestamp (second granularity).
Op 11: 0x3b91026f...a31bb79c
Relayer Wraps Tx
Eth tx → Canton BlockProposal
Validator2 — Re-execute
participant2 · REVM re-execution
Validator3 — Re-execute
participant3 · REVM re-execution
Illustrative visualization. Canton commits Command → Consensus → Finalization atomically within a single transaction, so individual Canton step durations are estimates. Measured anchors from on-chain timestamps: Canton record time → synchronizer effective time, and effective time → EVM block timestamp (second granularity).