← previous blocknext block →recent activity
Analyzing
Block #85,176,351
19 transactions · 17 stateful · 2026-07-02 19:36:57 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,176,351 · 19 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
2w04w16w07w18w29w310w411w512w616w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6418d68…bdc5
0x34b655…2a6f
14 touches
21 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
14 touches
21 conflicts
0x51a914cf…a822
0x34b655…2a6f
14 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
14 touches
21 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
14 touches
21 conflicts
0xb9bc1dfc…6bfb
0x34b655…2a6f
12 touches
15 conflicts
0x061d4e20…b84b
0x34b655…2a6f
8 touches
6 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 0xd6418d68d8…e2bdc5
Audit this contract →
← previous block·next block →recent activity