← previous blocknext block →recent activity
Analyzing
Block #88,354,551
61 transactions · 54 stateful · 2026-07-17 13:28:03 UTC
Parallelism
61/100
Blocked
70%
Avg conflicts / tx
3.31
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #88,354,551 · 61 txs across 24 waves · depth 24
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
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w38w09w110w211w328w445w547w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
24 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0xebac0f82…a49c
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x0c9eb6ea…7c39
0x34b655…2a6f
14 touches
21 conflicts
0x02991b41…19e6
0x34b655…2a6f
12 touches
15 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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity