← previous blocknext block →recent activity
Analyzing
Block #88,366,219
57 transactions · 52 stateful · 2026-07-17 14:46:56 UTC
Parallelism
68/100
Blocked
69%
Avg conflicts / tx
2.51
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #88,366,219 · 57 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w18w09w010w111w212w330w431w232w538w539w246w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x29c1a140…099f
0x34b655…2a6f
14 touches
21 conflicts
0xff196840…a453
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x2d651956…12e8
0x34b655…2a6f
10 touches
10 conflicts
0x6e1cd42e…1f23
0x34b655…2a6f
8 touches
6 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 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity