← previous blocknext block →recent activity
Analyzing
Block #85,707,010
11 transactions · 9 stateful · 2026-07-05 06:32:12 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,707,010 · 11 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
5w06w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49d02518…ca01
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x33ed0f4f…5e5c
0x40c49f…2af0
2 touches
0 conflicts
0x752ccdf3…2b99
0x40c49f…2af0
2 touches
0 conflicts
0xacb36d1d…0da2
0x40c49f…2af0
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 0x49d02518bb…c7ca01
Audit this contract →
← previous block·next block →recent activity