← previous blocknext block →recent activity
Analyzing
Block #85,199,722
10 transactions · 9 stateful · 2026-07-02 22:12:38 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,199,722 · 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
2w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2a605ba…d51e
0x34b655…2a6f
4 touches
1 conflict
0xd63e616b…a07d
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x23c7063a…399c
0x34b655…2a6f
4 touches
1 conflict
0x67d8b378…f2f8
0x34b655…2a6f
4 touches
1 conflict
0x1a6b3787…a9e6
0x34b655…2a6f
2 touches
0 conflicts
0x1af777a9…b403
0x34b655…2a6f
2 touches
0 conflicts
0x1ca5aec6…c1e1
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 0xd2a605baa9…a7d51e
Audit this contract →
← previous block·next block →recent activity