← previous blocknext block →recent activity
Analyzing
Block #85,176,137
29 transactions · 24 stateful · 2026-07-02 19:35:31 UTC
Parallelism
72/100
Blocked
71%
Avg conflicts / tx
1.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,176,137 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w39w411w012w113w214w315w416w517w618w720w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x731e6d82…2883
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity