← previous blocknext block →recent activity
Analyzing
Block #85,175,087
72 transactions · 56 stateful · 2026-07-02 19:28:30 UTC
Parallelism
71/100
Blocked
75%
Avg conflicts / tx
3.75
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #85,175,087 · 72 txs across 21 waves · depth 21
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
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w09w112w213w016w117w218w319w420w521w622w723w824w925w1055w158w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
34 touches
136 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
22 touches
55 conflicts
0x987aeb55…0e2a
0xa6afd3…d132
18 touches
36 conflicts
0xa678cd56…4fab
0x34b655…2a6f
18 touches
36 conflicts
0x3e1c3586…83d7
0xa6afd3…d132
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
16 touches
28 conflicts
0x826cce18…251c
0x34b655…2a6f
16 touches
28 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
136 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity