← previous blocknext block →recent activity
Analyzing
Block #85,772,505
10 transactions · 9 stateful · 2026-07-05 13:48:07 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,772,505 · 10 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
2w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06c59b8c…89c0
0x34b655…2a6f
6 touches
3 conflicts
0x61684cf2…e923
0x34b655…2a6f
6 touches
3 conflicts
0x894c3474…190f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1d720942…075a
0x34b655…2a6f
5 touches
3 conflicts
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x23d6b70a…c91a
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
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 0x06c59b8c41…2989c0
Audit this contract →
← previous block·next block →recent activity