← previous blocknext block →recent activity
Analyzing
Block #85,146,465
21 transactions · 18 stateful · 2026-07-02 16:18:02 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,146,465 · 21 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
1w03w15w06w07w116w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x58603063…4ef0
0x34b655…2a6f
8 touches
6 conflicts
0xaff2b8cb…8aff
0x34b655…2a6f
8 touches
6 conflicts
0x11431f9d…42c5
0x34b655…2a6f
4 touches
1 conflict
0x33ab05bd…d1d6
0x34b655…2a6f
4 touches
1 conflict
0x52e5f417…dbb0
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x69941f7e…3b1d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity