← previous blocknext block →recent activity
Analyzing
Block #80,464,602
23 transactions · 22 stateful · 2026-06-10 23:45:46 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,464,602 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w07w08w110w117w218w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x1c7763f6…89be
0x34b655…2a6f
6 touches
3 conflicts
0xc986d456…7074
0xd32edf…ff58
5 touches
3 conflicts
0x94a3fb3f…7515
0x34b655…2a6f
4 touches
1 conflict
0xf8f1e808…a4fd
0x34b655…2a6f
4 touches
1 conflict
0xfff39462…a61b
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x2e4eea52…0c68
0xc8689a…ee79
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity