← previous blocknext block →recent activity
Analyzing
Block #73,808,012
18 transactions · 16 stateful · 2026-05-11 03:36:56 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,808,012 · 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
4w06w18w09w111w215w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x45c3b05e…238f
0xd32edf…ff58
5 touches
3 conflicts
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0x3df3de0d…cd8b
0x34b655…2a6f
4 touches
1 conflict
0x59ef13ba…2741
0x34b655…2a6f
4 touches
1 conflict
0x6d0c65d9…c36f
0x34b655…2a6f
4 touches
1 conflict
0x8240d70c…7c3b
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
3 conflicts on slot 0xa91c899f02…fa6ee3
Audit this contract →
← previous block·next block →recent activity