← previous blocknext block →recent activity
Analyzing
Block #80,930,380
13 transactions · 9 stateful · 2026-06-13 03:32:29 UTC
Parallelism
77/100
Blocked
22%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,930,380 · 13 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
5w08w111w012w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d68c976…b6e6
0x34b655…2a6f
6 touches
3 conflicts
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe53bf2cb…5015
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
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
3 conflicts on slot 0x1d68c97607…23b6e6
Audit this contract →
← previous block·next block →recent activity