← previous blocknext block →recent activity
Analyzing
Block #85,142,035
23 transactions · 21 stateful · 2026-07-02 15:48:30 UTC
Parallelism
65/100
Blocked
52%
Avg conflicts / tx
1.52
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,142,035 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w410w511w612w716w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ae63663…9d94
0x34b655…2a6f
16 touches
28 conflicts
0x97c67486…27fe
0x34b655…2a6f
16 touches
28 conflicts
0xffb8950c…23c6
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xc83310b1…c778
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 conflicts
0xc99e7125…81b1
0x34b655…2a6f
14 touches
21 conflicts
0x4de29483…2a26
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
28 conflicts on slot 0x7ae6366345…ef9d94
Audit this contract →
← previous block·next block →recent activity