← previous blocknext block →recent activity

Analyzing

Block #73,396,128

16 transactions · 14 stateful · 2026-05-09 05:40:06 UTC

Parallelism

75/100

Blocked

21%

Avg conflicts / tx

0.25

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,396,128  ·  16 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

0x9ab0e28e…a3bc

0xd32edf…ff58

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x4db71e3e…8896

0x065c9d…c394

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0xa980598e…ec52

0x3bd359…433a

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x110738b1…ed0c

0x754704…b603

2 touches
0 conflicts

0x1e349dde…a33a

0x754704…b603

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

3 conflicts on slot 0x9ab0e28e43…b9a3bc

← previous block·next block →recent activity