← previous blocknext block →recent activity
Analyzing
Block #85,182,069
18 transactions · 17 stateful · 2026-07-02 20:15:06 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,182,069 · 18 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
3w04w111w012w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x086db8fc…0024
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfc366eef…6209
0x34b655…2a6f
5 touches
3 conflicts
0x0aa5b76b…60db
0x34b655…2a6f
4 touches
1 conflict
0x2b111712…0e59
0x34b655…2a6f
4 touches
1 conflict
0x2bad7381…b1a3
0x34b655…2a6f
4 touches
1 conflict
0x465f6ade…b8fc
0x34b655…2a6f
4 touches
1 conflict
0x744e0a36…70f7
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 0x086db8fc6e…830024
Audit this contract →
← previous block·next block →recent activity