← previous blocknext block →recent activity
Analyzing
Block #85,169,073
9 transactions · 8 stateful · 2026-07-02 18:48:30 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,169,073 · 9 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37421b44…45b5
0x34b655…2a6f
4 touches
1 conflict
0x89fd9eab…7bb2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x1863f229…e5f4
0x34b655…2a6f
2 touches
0 conflicts
0x191d5f81…65e3
0x34b655…2a6f
2 touches
0 conflicts
0x342a12bc…c045
0x34b655…2a6f
2 touches
0 conflicts
0x3923cd2c…e6d3
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 0x37421b44fd…6245b5
Audit this contract →
← previous block·next block →recent activity