← previous blocknext block →recent activity
Analyzing
Block #88,359,008
35 transactions · 33 stateful · 2026-07-17 13:58:11 UTC
Parallelism
69/100
Blocked
67%
Avg conflicts / tx
1.69
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #88,359,008 · 35 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
1w02w13w24w35w47w08w19w210w312w013w114w215w316w419w521w731w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xfcff8401…768e
0xd32edf…ff58
9 touches
10 conflicts
0x1e166a45…98a7
0x34b655…2a6f
8 touches
6 conflicts
0x35a9f06c…7689
0x34b655…2a6f
8 touches
6 conflicts
0x4a870d86…79ef
0x336ed4…c59c
8 touches
6 conflicts
0xc88f593e…5d93
0x336ed4…c59c
8 touches
6 conflicts
0x42041fec…bd86
0x754704…b603
8 touches
6 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity