← previous blocknext block →recent activity
Analyzing
Block #85,133,157
56 transactions · 50 stateful · 2026-07-02 14:49:16 UTC
Parallelism
64/100
Blocked
66%
Avg conflicts / tx
2.91
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #85,133,157 · 56 txs across 20 waves · depth 20
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
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w28w09w011w112w214w315w417w536w637w740w541w642w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xa678cd56…4fab
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x3e1c3586…83d7
0xa6afd3…d132
10 touches
10 conflicts
0x987aeb55…0e2a
0xa6afd3…d132
10 touches
10 conflicts
0xaa99c369…263d
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity