← previous blocknext block →recent activity
Analyzing
Block #85,129,137
43 transactions · 37 stateful · 2026-07-02 14:22:23 UTC
Parallelism
67/100
Blocked
65%
Avg conflicts / tx
1.72
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #85,129,137 · 43 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w19w110w211w212w313w014w115w217w019w220w021w122w223w324w427w428w135w637w840w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xd06fb4dc…5204
0x34b655…2a6f
8 touches
6 conflicts
0x9118b03c…cf12
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x6b1259e6…4e0e
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity