← previous blocknext block →recent activity
Analyzing
Block #88,359,548
23 transactions · 20 stateful · 2026-07-17 14:01:48 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,359,548 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w19w012w014w115w217w219w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13aceb70…cf9f
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0x516d95f0…79e5
0x34b655…2a6f
4 touches
1 conflict
0x77830e75…7f31
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8077aa91…b91e
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
6 conflicts on slot 0x13aceb701e…58cf9f
Audit this contract →
← previous block·next block →recent activity