← previous blocknext block →recent activity
Analyzing
Block #85,524,032
12 transactions · 10 stateful · 2026-07-04 10:12:24 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,524,032 · 12 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
2w03w17w08w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x830b63a6…8105
0x34b655…2a6f
4 touches
1 conflict
0x50887223…db7f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x33da96fe…4453
0x34b655…2a6f
2 touches
0 conflicts
0x568b02ef…f83a
0x34b655…2a6f
2 touches
0 conflicts
0x8210fa51…bc92
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 0x830b63a692…148105
Audit this contract →
← previous block·next block →recent activity