← previous blocknext block →recent activity
Analyzing
Block #85,146,361
28 transactions · 22 stateful · 2026-07-02 16:17:20 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,146,361 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w110w011w112w213w315w016w017w020w022w124w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x264f7d7d…8444
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xe732567d…b65d
0x34b655…2a6f
8 touches
6 conflicts
0xd2a592d9…1a96
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xa678cd56…4fab
0x34b655…2a6f
6 touches
3 conflicts
0x2b220e74…0724
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
6 conflicts on slot 0x264f7d7d7c…ee8444
Audit this contract →
← previous block·next block →recent activity