← previous blocknext block →recent activity
Analyzing
Block #88,351,264
40 transactions · 34 stateful · 2026-07-17 13:05:58 UTC
Parallelism
60/100
Blocked
59%
Avg conflicts / tx
2.3
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #88,351,264 · 40 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w29w010w111w212w317w318w420w521w630w731w832w933w1038w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xb9834665…e363
0x34b655…2a6f
12 touches
15 conflicts
0xf565ea1f…4245
0x34b655…2a6f
10 touches
10 conflicts
0x31616f97…1acc
0x34b655…2a6f
10 touches
10 conflicts
0x7b55198a…b946
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xebac0f82…a49c
0x34b655…2a6f
10 touches
10 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity