← previous blocknext block →recent activity

Analyzing

Block #73,986,666

10 transactions · 7 stateful · 2026-05-11 23:27:34 UTC

Parallelism

70/100

Blocked

29%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,986,666  ·  10 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

0xa15427f6…d932

0x34b655…2a6f

4 touches
1 conflict

0xb91a6f59…722c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x05638a8b…d586

0x34b655…2a6f

2 touches
0 conflicts

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x17dc7cd4…6e9d

0x34b655…2a6f

2 touches
0 conflicts

0x192cb36c…648d

0x34b655…2a6f

2 touches
0 conflicts

0x33f2d9b1…b689

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 0xa15427f6ca…8bd932

← previous block·next block →recent activity