← previous blocknext block →recent activity
Analyzing
Block #86,884,118
21 transactions · 18 stateful · 2026-07-10 17:33:17 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,884,118 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w09w110w211w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xe2ce91e2…b99e
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf726e2e2…e561
0x34b655…2a6f
6 touches
3 conflicts
0x6fa48528…fdbd
0x34b655…2a6f
6 touches
3 conflicts
0x78d79dcd…a930
0x34b655…2a6f
6 touches
3 conflicts
0xb0446875…2b96
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity