← previous blocknext block →recent activity
Analyzing
Block #85,181,235
13 transactions · 12 stateful · 2026-07-02 20:09:31 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,181,235 · 13 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
2w07w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a36c85b…96a5
0x34b655…2a6f
4 touches
1 conflict
0xb44564d6…bb43
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
2 touches
0 conflicts
0x0faa4d21…0acf
0x34b655…2a6f
2 touches
0 conflicts
0x23253ea8…e0a4
0x34b655…2a6f
2 touches
0 conflicts
0x307d4d49…6f08
0x34b655…2a6f
2 touches
0 conflicts
0x3d352bc9…4895
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 0x9a36c85bd5…bc96a5
Audit this contract →
← previous block·next block →recent activity