← previous blocknext block →recent activity
Analyzing
Block #85,408,267
21 transactions · 17 stateful · 2026-07-03 21:21:41 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,408,267 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w18w09w010w111w214w315w216w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x66f473d3…2d03
0xa6afd3…d132
6 touches
3 conflicts
0x424b80e6…8d09
0x34b655…2a6f
4 touches
1 conflict
0x54b193ad…c830
0x34b655…2a6f
4 touches
1 conflict
0x56c55026…fd69
0x34b655…2a6f
4 touches
1 conflict
0x6d471d3a…7d93
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
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