← previous blocknext block →recent activity

Analyzing

Block #74,456,323

11 transactions · 8 stateful · 2026-05-14 03:33:38 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,456,323  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x111f72de…b33c

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0x7b97d40a…09ed

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x233c53…b4cd

2 touches
0 conflicts

0x0711ec2d…d973

0x34b655…2a6f

2 touches
0 conflicts

0x313f2565…5b00

0x34b655…2a6f

2 touches
0 conflicts

0x57de3828…3fbb

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x34b6552d…112a6f

1 conflict on slot 0x111f72de15…fdb33c

← previous block·next block →recent activity