← previous blocknext block →recent activity
Analyzing
Block #85,145,717
15 transactions · 13 stateful · 2026-07-02 16:13:02 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,145,717 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w012w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x006c3b86…59a9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x44429a9b…771d
0x34b655…2a6f
2 touches
0 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
2 touches
0 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x006c3b8659…7a59a9
Audit this contract →
← previous block·next block →recent activity