← previous blocknext block →recent activity
Analyzing
Block #85,129,033
40 transactions · 36 stateful · 2026-07-02 14:21:41 UTC
Parallelism
75/100
Blocked
67%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,129,033 · 40 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
1w02w03w14w05w16w27w38w49w510w614w127w128w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0x1b3114cd…5e2d
0xa6afd3…d132
14 touches
21 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
12 touches
15 conflicts
0x6167486f…db40
0x34b655…2a6f
12 touches
15 conflicts
0x79fade94…7f93
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
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