← previous blocknext block →recent activity
Analyzing
Block #80,328,921
22 transactions · 19 stateful · 2026-06-10 08:41:40 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,328,921 · 22 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
1w03w18w210w011w114w015w118w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4afaa2f…3b69
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x771a3650…01cd
0x3bd359…433a
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
4 touches
1 conflict
0x8cf3d245…1d0d
0x69df8a…6292
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: 0xa6afd386…b0d132
3 conflicts on slot 0xe4afaa2f27…943b69
Audit this contract →
← previous block·next block →recent activity