← previous blocknext block →recent activity
Analyzing
Block #85,188,284
23 transactions · 21 stateful · 2026-07-02 20:56:25 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
1.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,188,284 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w07w18w29w310w411w513w114w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xdcf90674…5bf6
0x34b655…2a6f
12 touches
15 conflicts
0x548145a9…cfce
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x51a914cf…a822
0x34b655…2a6f
10 touches
10 conflicts
0x63b15849…80b2
0x34b655…2a6f
10 touches
10 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
10 touches
10 conflicts
0xf4319cfc…bab1
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity