← previous blocknext block →recent activity
Analyzing
Block #85,366,832
9 transactions · 7 stateful · 2026-07-03 16:45:50 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,366,832 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
6 touches
3 conflicts
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xac39df03…4bf6
0x34b655…2a6f
4 touches
1 conflict
0x16b46055…343e
0x34b655…2a6f
4 touches
1 conflict
0x13af9e48…d72a
0x34b655…2a6f
2 touches
0 conflicts
0x577f1c99…9ea3
0x34b655…2a6f
2 touches
0 conflicts
0x72fd59f1…b722
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
3 conflicts on slot 0x1aaf499609…4665ec
Audit this contract →
← previous block·next block →recent activity