← previous blocknext block →recent activity
Analyzing
Block #80,630,159
14 transactions · 9 stateful · 2026-06-11 18:10:35 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,630,159 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xe5a10916…8ad0
0xa6afd3…d132
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
2 touches
0 conflicts
0x894da4a3…a74e
0x34b655…2a6f
2 touches
0 conflicts
0x957c875f…b3f9
0x34b655…2a6f
2 touches
0 conflicts
0xab429b9f…6378
0x34b655…2a6f
2 touches
0 conflicts
0xb2fa1675…4e07
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity