← previous blocknext block →recent activity
Analyzing
Block #88,356,359
52 transactions · 47 stateful · 2026-07-17 13:40:22 UTC
Parallelism
69/100
Blocked
72%
Avg conflicts / tx
2.58
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #88,356,359 · 52 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
1w05w06w17w28w39w412w015w116w217w318w419w520w636w337w138w439w540w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x351d96b9…c5df
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: 0x48cba278…e2b48b
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity