← previous blocknext block →recent activity

Analyzing

Block #73,533,632

18 transactions · 10 stateful · 2026-05-09 20:55:01 UTC

Parallelism

78/100

Blocked

30%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,533,632  ·  18 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

0xf2472788…7eaf

0xd32edf…ff58

7 touches
6 conflicts

0xecab0eb6…ae4c

0x065c9d…c394

2 touches
0 conflicts

0xa4e3b3b1…0911

0x2a68ba…90c5

2 touches
0 conflicts

0xae69c125…2379

0x2a68ba…90c5

2 touches
0 conflicts

0xa980598e…ec52

0x3bd359…433a

2 touches
0 conflicts

0x4e437ae2…fecd

0x754704…b603

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

2 touches
0 conflicts

0x0fc41e7b…6831

0x98dc6e…8633

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 0xf24727884e…a37eaf

← previous block·next block →recent activity