← previous blocknext block →recent activity

Analyzing

Block #73,964,783

12 transactions · 7 stateful · 2026-05-11 21:00:48 UTC

Parallelism

83/100

Blocked

14%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,964,783  ·  12 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

0xf6476f21…3580

0x34b655…2a6f

4 touches
1 conflict

0xb91a6f59…722c

0x34b655…2a6f

4 touches
1 conflict

0xc4ac64a3…ebbc

0x34b655…2a6f

4 touches
1 conflict

0x037849a8…fa88

0x34b655…2a6f

2 touches
0 conflicts

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x33f2d9b1…b689

0x34b655…2a6f

2 touches
0 conflicts

0x543e0ab2…8201

0x34b655…2a6f

2 touches
0 conflicts

0x9ea57326…329f

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 0xf6476f21e7…f83580

← previous block·next block →recent activity