← previous blocknext block →recent activity
Analyzing
Block #85,141,326
18 transactions · 16 stateful · 2026-07-02 15:43:47 UTC
Parallelism
61/100
Blocked
38%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,141,326 · 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
3w04w15w26w37w48w59w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7e59d30…11dd
0x34b655…2a6f
14 touches
21 conflicts
0x323b1101…aa67
0x34b655…2a6f
14 touches
21 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
14 touches
21 conflicts
0xf28082df…312c
0x34b655…2a6f
14 touches
21 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
14 touches
21 conflicts
0xffb8950c…23c6
0x34b655…2a6f
14 touches
21 conflicts
0x9966da31…0d0f
0x34b655…2a6f
14 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 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 0xf7e59d3053…0611dd
Audit this contract →
← previous block·next block →recent activity