← previous blocknext block →recent activity
Analyzing
Block #85,215,328
18 transactions · 18 stateful · 2026-07-02 23:56:32 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,215,328 · 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
2w04w05w06w18w010w211w112w114w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bdb9869…7558
0x34b655…2a6f
8 touches
6 conflicts
0x23f427c5…74ff
0x065c9d…c394
4 touches
1 conflict
0xfadd9498…97e9
0x065c9d…c394
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x5238dcb7…e0e2
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x5d4a3441…e31c
0x34b655…2a6f
4 touches
1 conflict
0x76bac032…590d
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
6 conflicts on slot 0x6bdb9869c7…427558
Audit this contract →
← previous block·next block →recent activity