← previous blocknext block →recent activity
Analyzing
Block #86,911,802
22 transactions · 18 stateful · 2026-07-10 20:38:21 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,911,802 · 22 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
5w06w17w28w010w311w419w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa42e8482…b88f
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6b2ba712…0214
0x34b655…2a6f
4 touches
1 conflict
0x74888025…a5b8
0x34b655…2a6f
4 touches
1 conflict
0x78a0d933…dde2
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
10 conflicts on slot 0xa42e848215…53b88f
Audit this contract →
← previous block·next block →recent activity