← previous blocknext block →recent activity
Analyzing
Block #80,167,956
25 transactions · 20 stateful · 2026-06-09 14:48:19 UTC
Parallelism
88/100
Blocked
40%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,167,956 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w210w111w012w116w220w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x8e60ff7c…1edf
0xd32edf…ff58
5 touches
3 conflicts
0xc8a10d9e…919f
0x34b655…2a6f
4 touches
1 conflict
0xe75ce681…ba5f
0x188d58…ea8e
4 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
0x729c91b8…9538
0x188d58…ea8e
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
3 conflicts on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity