← previous blocknext block →recent activity
Analyzing
Block #85,175,105
10 transactions · 9 stateful · 2026-07-02 19:28:38 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,175,105 · 10 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43e2eda1…396f
0x34b655…2a6f
4 touches
1 conflict
0x655cb8f1…89a6
0x34b655…2a6f
4 touches
1 conflict
0xde30e1bc…7c51
0x34b655…2a6f
4 touches
1 conflict
0x043488e6…2455
0x34b655…2a6f
2 touches
0 conflicts
0x08d66073…e706
0x34b655…2a6f
2 touches
0 conflicts
0x1ca5aec6…c1e1
0x34b655…2a6f
2 touches
0 conflicts
0x1cbcd969…eeb7
0x34b655…2a6f
2 touches
0 conflicts
0x1f1e2d4e…07e0
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 0x43e2eda154…aa396f
Audit this contract →
← previous block·next block →recent activity