← previous blocknext block →recent activity
Analyzing
Block #80,217,646
23 transactions · 23 stateful · 2026-06-09 20:19:48 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,217,646 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w07w08w19w210w315w417w018w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x52d65d97…1c96
0xa6afd3…d132
6 touches
3 conflicts
0x11f2aded…153a
0x34b655…2a6f
4 touches
1 conflict
0x1a46cad8…33f1
0x34b655…2a6f
4 touches
1 conflict
0x49dbd975…bae1
0x34b655…2a6f
4 touches
1 conflict
0x5d3fe086…0307
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity