← previous blocknext block →recent activity
Analyzing
Block #85,611,970
16 transactions · 16 stateful · 2026-07-04 19:58:02 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
1.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,611,970 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w110w211w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
10 touches
10 conflicts
0x069b18e0…deae
0x34b655…2a6f
10 touches
10 conflicts
0x7ea53c99…0c3e
0x34b655…2a6f
8 touches
6 conflicts
0xef02ed46…48a4
0x34b655…2a6f
6 touches
3 conflicts
0x178db37f…debb
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
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
15 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity