← previous blocknext block →recent activity

Analyzing

Block #74,456,304

12 transactions · 11 stateful · 2026-05-14 03:33:30 UTC

Parallelism

75/100

Blocked

18%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,456,304  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x8cc18498…ce7e

0x34b655…2a6f

4 touches
1 conflict

0x59a54ff4…d21b

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0711ec2d…d973

0x34b655…2a6f

2 touches
0 conflicts

0x0d3d3160…bb17

0x34b655…2a6f

2 touches
0 conflicts

0x28c180e1…f1e2

0x34b655…2a6f

2 touches
0 conflicts

0x414e9446…4b59

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 0x8cc18498cc…52ce7e

← previous block·next block →recent activity