← previous blocknext block →recent activity
Analyzing
Block #85,176,011
17 transactions · 17 stateful · 2026-07-02 19:34:41 UTC
Parallelism
53/100
Blocked
41%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,176,011 · 17 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
2w03w14w25w36w47w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xceb535f3…19cf
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
12 touches
15 conflicts
0x51a914cf…a822
0x34b655…2a6f
12 touches
15 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
12 touches
15 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
12 touches
15 conflicts
0x9966da31…0d0f
0x34b655…2a6f
12 touches
15 conflicts
0xe47478a3…a058
0x34b655…2a6f
12 touches
15 conflicts
0xf7e59d30…11dd
0x34b655…2a6f
12 touches
15 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 0xceb535f356…6319cf
Audit this contract →
← previous block·next block →recent activity