← previous blocknext block →recent activity
Analyzing
Block #88,344,137
61 transactions · 53 stateful · 2026-07-17 12:18:15 UTC
Parallelism
67/100
Blocked
79%
Avg conflicts / tx
3.05
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #88,344,137 · 61 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w19w210w311w112w413w214w315w416w539w240w342w643w746w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0002
0x48cba2…b48b
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xc9dce17a…a1a1
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0x33253e31…54b8
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity