← previous blocknext block →recent activity
Analyzing
Block #85,129,637
31 transactions · 26 stateful · 2026-07-02 14:25:44 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,129,637 · 31 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
1w04w15w27w08w111w014w015w116w217w321w123w225w229w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x7fffd49d…772a
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xcccbf465…4c06
0x34b655…2a6f
6 touches
3 conflicts
0x5ad3280d…16bb
0x34b655…2a6f
6 touches
3 conflicts
0x264f7d7d…8444
0x34b655…2a6f
6 touches
3 conflicts
0xae5c6d70…aedc
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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