← previous blocknext block →recent activity
Analyzing
Block #85,162,168
21 transactions · 19 stateful · 2026-07-02 18:02:33 UTC
Parallelism
76/100
Blocked
21%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,162,168 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5337754c…a27f
0x34b655…2a6f
10 touches
10 conflicts
0xbc8ead31…90fd
0x34b655…2a6f
10 touches
10 conflicts
0xabd0fca8…b1d4
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x06aed19e…ca57
0x34b655…2a6f
8 touches
6 conflicts
0x2d6d55b0…b6eb
0x34b655…2a6f
8 touches
6 conflicts
0x548145a9…cfce
0x34b655…2a6f
8 touches
6 conflicts
0x63b15849…80b2
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
10 conflicts on slot 0x5337754ce7…3ea27f
Audit this contract →
← previous block·next block →recent activity