← previous blocknext block →recent activity
Analyzing
Block #85,175,116
18 transactions · 15 stateful · 2026-07-02 19:28:42 UTC
Parallelism
61/100
Blocked
60%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,175,116 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w310w411w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
6 touches
3 conflicts
0x2b268fa9…eba2
0x34b655…2a6f
6 touches
3 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
6 touches
3 conflicts
0x6167486f…db40
0x34b655…2a6f
6 touches
3 conflicts
0x765cd07a…1018
0x34b655…2a6f
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
6 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity