← previous blocknext block →recent activity
Analyzing
Block #85,138,534
25 transactions · 23 stateful · 2026-07-02 15:25:08 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,138,534 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w29w010w011w112w213w316w417w320w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x126a0344…4465
0x34b655…2a6f
8 touches
6 conflicts
0xfadc118d…5d64
0x34b655…2a6f
6 touches
3 conflicts
0x4caf91f9…8ab5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6d99ac64…0aa3
0x34b655…2a6f
6 touches
3 conflicts
0x644919d7…9727
0x34b655…2a6f
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity