← previous blocknext block →recent activity
Analyzing
Block #86,835,933
15 transactions · 13 stateful · 2026-07-10 12:11:03 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,835,933 · 15 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
3w04w05w16w210w211w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xedcfbee7…ea97
0x34b655…2a6f
4 touches
1 conflict
0xf47128a0…896a
0x34b655…2a6f
4 touches
1 conflict
0x361cb4cb…4aae
0x34b655…2a6f
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity