← previous blocknext block →recent activity
Analyzing
Block #85,536,084
10 transactions · 7 stateful · 2026-07-04 11:32:38 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,536,084 · 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
5w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b3da897…b268
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x11b46051…699a
0x34b655…2a6f
2 touches
0 conflicts
0x2336ab39…d5df
0x34b655…2a6f
2 touches
0 conflicts
0x6b42cd19…c06b
0x34b655…2a6f
2 touches
0 conflicts
0x830b63a6…8105
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 0x7b3da897ce…abb268
Audit this contract →
← previous block·next block →recent activity