← previous blocknext block →recent activity
Analyzing
Block #85,160,777
21 transactions · 19 stateful · 2026-07-02 17:53:16 UTC
Parallelism
52/100
Blocked
47%
Avg conflicts / tx
1.76
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,160,777 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x06aed19e…ca57
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 conflicts
0x548145a9…cfce
0x34b655…2a6f
16 touches
28 conflicts
0x63b15849…80b2
0x34b655…2a6f
16 touches
28 conflicts
0xb44d5376…33cc
0x34b655…2a6f
16 touches
28 conflicts
0xa1571d54…ae41
0x34b655…2a6f
16 touches
28 conflicts
0x206b3b18…aafe
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity