← previous blocknext block →recent activity
Analyzing
Block #88,359,969
28 transactions · 25 stateful · 2026-07-17 14:04:39 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.29
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #88,359,969 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w19w113w215w318w319w420w521w622w725w827w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xffc2f21e…b393
0x34b655…2a6f
10 touches
10 conflicts
0x8eb5f632…c9eb
0x34b655…2a6f
10 touches
10 conflicts
0x24022e42…7c2a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xcadc2eec…bbf5
0x34b655…2a6f
6 touches
3 conflicts
0x124be23b…2cca
0x34b655…2a6f
4 touches
2 conflicts
0x00bbd28c…e227
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity