← previous blocknext block →recent activity
Analyzing
Block #86,856,733
24 transactions · 21 stateful · 2026-07-10 14:30:02 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,856,733 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w412w015w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
14 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xf58b2d27…e4eb
0x34b655…2a6f
8 touches
6 conflicts
0x45877cba…0b50
0x34b655…2a6f
6 touches
3 conflicts
0x48b8d2e5…3f2f
0x34b655…2a6f
6 touches
3 conflicts
0x666b28db…11f0
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x85440df6…832c
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity