← previous blocknext block →recent activity
Analyzing
Block #85,105,474
20 transactions · 11 stateful · 2026-07-02 11:44:08 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,105,474 · 20 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0xe6d4c76c…2179
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0xffb8950c…23c6
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x23961159…1e02
0x34b655…2a6f
6 touches
3 conflicts
0x3a041575…77bb
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity