← previous blocknext block →recent activity
Analyzing
Block #88,356,558
73 transactions · 63 stateful · 2026-07-17 13:41:45 UTC
Parallelism
66/100
Blocked
81%
Avg conflicts / tx
4.07
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #88,356,558 · 73 txs across 25 waves · depth 25
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
wave w24
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w38w49w538w139w240w641w547w348w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x00000000…0002
0x48cba2…b48b
24 touches
66 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
16 touches
28 conflicts
0x7525206c…fbd5
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x7e5ea60a…c4aa
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
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity