← previous blocknext block →recent activity
Analyzing
Block #88,355,874
89 transactions · 73 stateful · 2026-07-17 13:37:03 UTC
Parallelism
76/100
Blocked
79%
Avg conflicts / tx
3.83
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #88,355,874 · 89 txs across 21 waves · depth 21
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w17w28w310w411w513w614w715w816w917w1043w648w768w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x889d5e90…929a
0x2a68ba…90c5
22 touches
55 conflicts
0x00000000…0002
0x48cba2…b48b
22 touches
55 conflicts
0x92385428…6941
0x34b655…2a6f
18 touches
36 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x006ee1d9…5485
0xa6afd3…d132
16 touches
28 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity