← previous blocknext block →recent activity
Analyzing
Block #85,126,004
24 transactions · 16 stateful · 2026-07-02 14:01:26 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,126,004 · 24 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
1w03w04w111w012w113w216w319w020w122w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x39619209…42e2
0x34b655…2a6f
4 touches
1 conflict
0x3fedc1cc…28f0
0x34b655…2a6f
4 touches
1 conflict
0x63271989…1a0e
0x34b655…2a6f
4 touches
1 conflict
0x63da0619…7a55
0x34b655…2a6f
4 touches
1 conflict
0x7523ad90…2ba5
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
3 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity