← previous blocknext block →recent activity
Analyzing
Block #80,502,220
24 transactions · 17 stateful · 2026-06-11 03:56:19 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,502,220 · 24 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
2w03w111w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
8 touches
6 conflicts
0x7fce0d8a…e843
0x34b655…2a6f
8 touches
6 conflicts
0xac0f2a19…d2e0
0x34b655…2a6f
8 touches
6 conflicts
0x2e4eea52…0c68
0xc8689a…ee79
8 touches
6 conflicts
0xaf498679…7732
0x34b655…2a6f
8 touches
6 conflicts
0x4da9d360…5fc6
0x34b655…2a6f
4 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
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