← previous blocknext block →recent activity
Analyzing
Block #80,230,733
14 transactions · 12 stateful · 2026-06-09 21:46:55 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,230,733 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
11w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x6d46d4bb…96e7
0x34b655…2a6f
2 touches
0 conflicts
0x90f07a4f…d932
0x34b655…2a6f
2 touches
0 conflicts
0xb138d087…4689
0x34b655…2a6f
2 touches
0 conflicts
0x09a15b10…2639
0x754704…b603
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
1 conflict on slot 0x070a562acf…648147
Audit this contract →
← previous block·next block →recent activity