← previous blocknext block →recent activity
Analyzing
Block #85,146,106
76 transactions · 59 stateful · 2026-07-02 16:15:38 UTC
Parallelism
74/100
Blocked
75%
Avg conflicts / tx
4
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #85,146,106 · 76 txs across 20 waves · depth 20
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
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w19w110w211w012w114w215w316w417w521w622w735w260w361w463w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
40 touches
190 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0x2b268fa9…eba2
0x34b655…2a6f
14 touches
21 conflicts
0x30153288…6d46
0x34b655…2a6f
14 touches
21 conflicts
0x301e1c77…9e30
0x34b655…2a6f
14 touches
21 conflicts
0x51087f5a…61f7
0x34b655…2a6f
14 touches
21 conflicts
0x7e1c758b…2f47
0x34b655…2a6f
14 touches
21 conflicts
0x826cce18…251c
0x34b655…2a6f
14 touches
21 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
190 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity