← previous blocknext block →recent activity

Analyzing

Block #73,651,922

17 transactions · 14 stateful · 2026-05-10 10:04:05 UTC

Parallelism

76/100

Blocked

43%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,651,922  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x63cf81e7…1337

0xd32edf…ff58

7 touches
6 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x23114fac…630a

0x34b655…2a6f

2 touches
0 conflicts

0x3b669e5a…f7a1

0x34b655…2a6f

2 touches
0 conflicts

0x3ded8a5b…3cf0

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: 0xd32edf66…9fff58

6 conflicts on slot 0x63cf81e769…ca1337

← previous block·next block →recent activity