← previous blocknext block →recent activity
Analyzing
Block #85,163,244
14 transactions · 13 stateful · 2026-07-02 18:09:42 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,163,244 · 14 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
1w02w13w28w011w112w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2207d3d…59ce
0x34b655…2a6f
10 touches
10 conflicts
0x06aed19e…ca57
0x34b655…2a6f
6 touches
3 conflicts
0x0c099894…79ca
0x34b655…2a6f
6 touches
3 conflicts
0x0dd6d5ef…ccf9
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x3c2c4784…d084
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 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
10 conflicts on slot 0xc2207d3d4e…b259ce
Audit this contract →
← previous block·next block →recent activity