← previous blocknext block →recent activity
Analyzing
Block #86,450,991
39 transactions · 35 stateful · 2026-07-08 17:16:04 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
1.97
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #86,450,991 · 39 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w08w19w210w311w412w513w614w715w816w920w322w223w425w526w534w1035w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x5d7f309d…5145
0x34b655…2a6f
12 touches
15 conflicts
0x6a023a3d…c184
0x34b655…2a6f
12 touches
15 conflicts
0x727fbce7…0c80
0x34b655…2a6f
12 touches
15 conflicts
0x7506443a…4820
0x34b655…2a6f
12 touches
15 conflicts
0x04105a34…6eea
0x34b655…2a6f
12 touches
15 conflicts
0x8388eab6…83ff
0x34b655…2a6f
12 touches
15 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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity