← previous blocknext block →recent activity
Analyzing
Block #85,185,062
36 transactions · 34 stateful · 2026-07-02 20:35:01 UTC
Parallelism
56/100
Blocked
68%
Avg conflicts / tx
2.31
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #85,185,062 · 36 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w311w013w014w115w216w317w418w519w621w722w423w524w125w226w828w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xfc366eef…6209
0x34b655…2a6f
8 touches
6 conflicts
0xc2207d3d…59ce
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity