← previous blocknext block →recent activity
Analyzing
Block #88,352,666
34 transactions · 32 stateful · 2026-07-17 13:15:20 UTC
Parallelism
68/100
Blocked
69%
Avg conflicts / tx
2.06
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #88,352,666 · 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
1w02w14w15w26w37w48w010w111w012w113w214w315w416w517w618w726w227w328w429w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xd39bb0c0…e051
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x93afca4c…b479
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0c9eb6ea…7c39
0x34b655…2a6f
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity