← previous blocknext block →recent activity
Analyzing
Block #85,145,964
23 transactions · 19 stateful · 2026-07-02 16:14:41 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,145,964 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w07w18w29w313w115w319w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d61a1c5…9fe6
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xebda062f…e87a
0x34b655…2a6f
6 touches
3 conflicts
0x30153288…6d46
0x34b655…2a6f
4 touches
1 conflict
0x3149127f…19a9
0x34b655…2a6f
4 touches
1 conflict
0x37421b44…45b5
0x34b655…2a6f
4 touches
1 conflict
0x3fd89215…bf0f
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 0x1d61a1c583…bf9fe6
Audit this contract →
← previous block·next block →recent activity