← previous blocknext block →recent activity

Analyzing

Block #73,920,933

18 transactions · 11 stateful · 2026-05-11 16:09:10 UTC

Parallelism

83/100

Blocked

36%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,920,933  ·  18 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

0xe248d1d0…cb73

0x065c9d…c394

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x1e90c175…798f

0xd32edf…ff58

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x264c6e4e…cbb6

0x3bd359…433a

2 touches
0 conflicts

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0003

0x5afd3e…7620

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

3 conflicts on slot 0xe248d1d06f…42cb73

← previous block·next block →recent activity