← previous blocknext block →recent activity
Analyzing
Block #86,966,903
9 transactions · 8 stateful · 2026-07-11 02:46:28 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,966,903 · 9 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
1w03w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x155dff63…2af8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x12573732…e891
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x29ef294a…272e
0x34b655…2a6f
2 touches
0 conflicts
0x5e2723f6…779d
0x34b655…2a6f
2 touches
0 conflicts
0x60c7217a…8c94
0x34b655…2a6f
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
3 conflicts on slot 0x155dff638e…a62af8
Audit this contract →
← previous block·next block →recent activity