← previous blocknext block →recent activity
Analyzing
Block #85,144,109
28 transactions · 26 stateful · 2026-07-02 16:02:20 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,144,109 · 28 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
3w04w15w06w18w09w110w211w319w121w022w224w426w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
6 touches
3 conflicts
0x6167486f…db40
0x34b655…2a6f
6 touches
3 conflicts
0x43e2eda1…396f
0x34b655…2a6f
4 touches
1 conflict
0x603a2623…ddf5
0x34b655…2a6f
4 touches
1 conflict
0x6509eb9e…949e
0x34b655…2a6f
4 touches
1 conflict
0x79f94908…8616
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity