← previous blocknext block →recent activity
Analyzing
Block #85,344,416
20 transactions · 19 stateful · 2026-07-03 14:16:25 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,344,416 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w07w18w29w112w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda2ee2e7…968a
0x34b655…2a6f
6 touches
3 conflicts
0x0e5f2a94…4732
0x34b655…2a6f
6 touches
3 conflicts
0xa0bf4c78…28e7
0x34b655…2a6f
6 touches
3 conflicts
0x2bf5914f…c75d
0x34b655…2a6f
6 touches
3 conflicts
0x37421b44…45b5
0x34b655…2a6f
4 touches
1 conflict
0x5af10b50…8d5c
0x34b655…2a6f
4 touches
1 conflict
0x665a59a6…79a6
0x34b655…2a6f
4 touches
1 conflict
0x6d73f5bf…53ea
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 0xda2ee2e777…e7968a
Audit this contract →
← previous block·next block →recent activity