← previous blocknext block →recent activity
Analyzing
Block #85,129,989
35 transactions · 32 stateful · 2026-07-02 14:28:05 UTC
Parallelism
77/100
Blocked
56%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,129,989 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w08w19w210w311w412w014w015w116w217w318w422w124w225w126w228w332w533w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x6fa99270…2038
0x34b655…2a6f
8 touches
6 conflicts
0x987aeb55…0e2a
0xa6afd3…d132
6 touches
3 conflicts
0x00ca5a7d…debb
0x34b655…2a6f
6 touches
3 conflicts
0x644919d7…9727
0x34b655…2a6f
6 touches
3 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
6 touches
3 conflicts
0x7fffd49d…772a
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity