← previous blocknext block →recent activity
Analyzing
Block #85,630,906
13 transactions · 11 stateful · 2026-07-04 22:04:05 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,630,906 · 13 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
1w04w05w16w17w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe7e126…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfa6aaad1…dd23
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x11d629eb…bcd9
0x34b655…2a6f
4 touches
1 conflict
0x1fe92c2a…cbb1
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 0x5fe7e1267e…896dd2
Audit this contract →
← previous block·next block →recent activity