← previous blocknext block →recent activity

Analyzing

Block #74,351,456

21 transactions · 14 stateful · 2026-05-13 15:55:30 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,351,456  ·  21 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

0xc4e19ae4…0788

0xe7cd86…c82d

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xbc04d98e…a484

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x047101a9…7111

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: 0xe7cd86e1…0fc82d

3 conflicts on slot 0xc4e19ae47e…dc0788

← previous block·next block →recent activity