← previous blocknext block →recent activity
Analyzing
Block #85,146,166
24 transactions · 23 stateful · 2026-07-02 16:16:02 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,146,166 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w39w417w019w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9966da31…0d0f
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xd2a592d9…1a96
0x34b655…2a6f
10 touches
10 conflicts
0xe732567d…b65d
0x34b655…2a6f
10 touches
10 conflicts
0xf2112d98…bb04
0x34b655…2a6f
10 touches
10 conflicts
0xf7e59d30…11dd
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xaedefef9…65a7
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x9966da3102…c80d0f
Audit this contract →
← previous block·next block →recent activity