← previous blocknext block →recent activity
Analyzing
Block #85,249,558
20 transactions · 16 stateful · 2026-07-03 03:44:37 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,249,558 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w010w112w115w016w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x987aeb55…0e2a
0xa6afd3…d132
4 touches
1 conflict
0x086db8fc…0024
0x34b655…2a6f
4 touches
1 conflict
0x5ad3280d…16bb
0x34b655…2a6f
4 touches
1 conflict
0x801058a8…5bc3
0x34b655…2a6f
4 touches
1 conflict
0xa7e2f1b7…7e6f
0x34b655…2a6f
4 touches
1 conflict
0xb9bc1dfc…6bfb
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity