← previous blocknext block →recent activity
Analyzing
Block #86,848,275
19 transactions · 17 stateful · 2026-07-10 13:33:29 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,848,275 · 19 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
2w06w07w110w111w217w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe6da3556…9a23
0x34b655…2a6f
4 touches
1 conflict
0x40287836…2dff
0x34b655…2a6f
4 touches
1 conflict
0xea297ef6…552d
0x34b655…2a6f
4 touches
1 conflict
0xea297ef6…552e
0x34b655…2a6f
4 touches
1 conflict
0x4067b2e9…83f6
0x34b655…2a6f
4 touches
1 conflict
0x505d32fe…14ad
0x34b655…2a6f
4 touches
1 conflict
0x7b67f6cf…0aab
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity