← previous blocknext block →recent activity
Analyzing
Block #85,570,903
74 transactions · 50 stateful · 2026-07-04 15:24:30 UTC
Parallelism
76/100
Blocked
78%
Avg conflicts / tx
2.86
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #85,570,903 · 74 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w09w110w211w312w013w114w215w318w420w421w523w624w562w163w664w665w766w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
36 touches
153 conflicts
0x15a8dcd6…2c36
0x34b655…2a6f
32 touches
120 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
32 touches
120 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
32 touches
120 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
32 touches
120 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
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
153 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity