← previous blocknext block →recent activity
Analyzing
Block #85,125,930
26 transactions · 22 stateful · 2026-07-02 14:00:57 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,125,930 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w211w012w013w114w215w116w017w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22d3c767…e4d1
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x4c033e0e…3242
0xd32edf…ff58
7 touches
6 conflicts
0x25de453d…9573
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
6 touches
3 conflicts
0x656bd53e…af4e
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 0x22d3c767ef…68e4d1
Audit this contract →
← previous block·next block →recent activity