← previous blocknext block →recent activity
Analyzing
Block #85,131,426
50 transactions · 47 stateful · 2026-07-02 14:37:42 UTC
Parallelism
80/100
Blocked
66%
Avg conflicts / tx
2.02
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,131,426 · 50 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w113w114w215w316w425w236w537w439w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0002
0x04fdea…47d7
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x66c5e348…51d0
0xa6afd3…d132
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x85631114…3ff6
0xa6afd3…d132
10 touches
10 conflicts
0x987aeb55…0e2a
0xa6afd3…d132
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity