← previous blocknext block →recent activity

Analyzing

Block #73,210,930

7 transactions · 6 stateful · 2026-05-08 09:08:04 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,210,930  ·  7 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

0xf387094c…f1de

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x151f4985…bc86

0x065c9d…c394

3 touches
1 conflict

0x3aa08214…f257

0x065c9d…c394

2 touches
0 conflicts

0x4675b769…b931

0x065c9d…c394

2 touches
0 conflicts

0x64979bde…ba46

0x065c9d…c394

2 touches
0 conflicts

0xa6f4fae7…411c

0x065c9d…c394

2 touches
0 conflicts

0x70b2f813…783c

0x2a68ba…90c5

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: 0x065c9d28…a9c394

1 conflict on slot 0xf387094c22…f8f1de

← previous block·next block →recent activity