← previous blocknext block →recent activity
Analyzing
Block #80,542,359
23 transactions · 16 stateful · 2026-06-11 08:23:30 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,542,359 · 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
1w02w13w27w18w09w110w211w316w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
8 touches
6 conflicts
0x11162862…9219
0x34b655…2a6f
8 touches
6 conflicts
0xaf498679…7732
0x34b655…2a6f
6 touches
3 conflicts
0x2e4eea52…0c68
0xc8689a…ee79
6 touches
3 conflicts
0x7fce0d8a…e843
0x34b655…2a6f
6 touches
3 conflicts
0x9e20cccf…19cc
0xa6afd3…d132
6 touches
3 conflicts
0x70fc592c…b20a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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
6 conflicts on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity