← previous blocknext block →recent activity
Analyzing
Block #86,856,079
24 transactions · 21 stateful · 2026-07-10 14:25:41 UTC
Parallelism
75/100
Blocked
67%
Avg conflicts / tx
1.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,856,079 · 24 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
1w02w13w27w08w19w210w311w412w513w114w316w417w318w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xdec5bfea…d17f
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x1ee44d08…7262
0x34b655…2a6f
6 touches
3 conflicts
0x216ffe66…1f94
0x34b655…2a6f
6 touches
3 conflicts
0x301e1c77…9e30
0x34b655…2a6f
6 touches
3 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
6 touches
3 conflicts
0x4dda64ff…13d5
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity