← previous blocknext block →recent activity
Analyzing
Block #80,654,797
70 transactions · 9 stateful · 2026-06-11 20:54:50 UTC
Parallelism
94/100
Blocked
33%
Avg conflicts / tx
0.09
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,654,797 · 70 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
9w023w140w258w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
8 touches
6 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
6 touches
3 conflicts
0x60d07066…695c
0x34b655…2a6f
6 touches
3 conflicts
0xcd6ccd20…c33e
0x34b655…2a6f
4 touches
1 conflict
0x12978194…d32f
0x34b655…2a6f
4 touches
1 conflict
0x773d2e1f…4f2d
0x34b655…2a6f
4 touches
1 conflict
0x47fe36d9…3b31
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
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
6 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity