← previous blocknext block →recent activity
Analyzing
Block #85,189,134
34 transactions · 27 stateful · 2026-07-02 21:02:06 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
1.65
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #85,189,134 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w010w111w212w117w018w119w220w321w422w524w425w127w728w232w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd06fb4dc…5204
0x34b655…2a6f
14 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x66c5e348…51d0
0xa6afd3…d132
8 touches
6 conflicts
0x85631114…3ff6
0xa6afd3…d132
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x1b3114cd…5e2d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
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
21 conflicts on slot 0xd06fb4dc7f…b55204
Audit this contract →
← previous block·next block →recent activity