← previous blocknext block →recent activity
Analyzing
Block #85,133,617
44 transactions · 35 stateful · 2026-07-02 14:52:20 UTC
Parallelism
66/100
Blocked
66%
Avg conflicts / tx
2.14
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #85,133,617 · 44 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w19w210w315w018w019w120w221w322w423w524w625w726w827w931w134w237w140w1241w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x765cd07a…1018
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
10 touches
10 conflicts
0x43ffd8bd…0d0c
0x34b655…2a6f
10 touches
10 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
10 touches
10 conflicts
0x7b3da897…b268
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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity