← previous blocknext block →recent activity
Analyzing
Block #85,049,944
20 transactions · 18 stateful · 2026-07-02 05:32:55 UTC
Parallelism
55/100
Blocked
50%
Avg conflicts / tx
1.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #85,049,944 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w412w516w517w619w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x4467ecee…e95b
0x34b655…2a6f
14 touches
21 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
12 touches
15 conflicts
0xe47478a3…a058
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x2762c9c6…100e
0x34b655…2a6f
10 touches
10 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
10 touches
10 conflicts
0xa1144aa9…7f67
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity