← previous blocknext block →recent activity
Analyzing
Block #86,667,210
10 transactions · 10 stateful · 2026-07-09 17:23:55 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,667,210 · 10 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
4w05w16w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b564d99…b9eb
0x34b655…2a6f
6 touches
3 conflicts
0x6b564d99…b9ec
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf8e84422…84a6
0x34b655…2a6f
6 touches
3 conflicts
0x59b0a8da…0928
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x6b564d99f6…83b9eb
Audit this contract →
← previous block·next block →recent activity