← previous blocknext block →recent activity
Analyzing
Block #85,529,178
9 transactions · 8 stateful · 2026-07-04 10:46:39 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,529,178 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda2ee2e7…968a
0x34b655…2a6f
6 touches
3 conflicts
0x2267f8c4…a571
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
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 0xda2ee2e777…e7968a
Audit this contract →
← previous block·next block →recent activity