← previous blocknext block →recent activity
Analyzing
Block #85,158,420
46 transactions · 37 stateful · 2026-07-02 17:37:38 UTC
Parallelism
63/100
Blocked
76%
Avg conflicts / tx
2.37
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #85,158,420 · 46 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w210w311w412w013w116w017w118w219w320w421w522w623w724w825w931w232w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0xc7cda03f…b9da
0x34b655…2a6f
12 touches
15 conflicts
0x94e7f277…471b
0x34b655…2a6f
12 touches
15 conflicts
0x3230277c…ef39
0xc8689a…ee79
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x2406ccf7…c1cb
0x34b655…2a6f
10 touches
10 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity