← previous blocknext block →recent activity
Analyzing
Block #86,850,003
51 transactions · 34 stateful · 2026-07-10 13:45:02 UTC
Parallelism
71/100
Blocked
68%
Avg conflicts / tx
2.33
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,850,003 · 51 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w111w012w117w018w119w220w321w422w523w624w725w826w927w1028w1129w1235w237w338w447w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x2fd12b6c…02cc
0x34b655…2a6f
10 touches
10 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
10 touches
10 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
10 touches
10 conflicts
0x505d32fe…14ad
0x34b655…2a6f
8 touches
6 conflicts
0x574628e9…dcc3
0x34b655…2a6f
8 touches
6 conflicts
0x85fed3a2…a604
0x34b655…2a6f
8 touches
6 conflicts
0x8e9c2af5…6960
0x34b655…2a6f
8 touches
6 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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity