← previous blocknext block →recent activity
Analyzing
Block #88,359,591
32 transactions · 20 stateful · 2026-07-17 14:02:05 UTC
Parallelism
88/100
Blocked
50%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,359,591 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w215w016w117w219w120w222w223w125w026w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0x804eb1a6…4593
0x34b655…2a6f
8 touches
6 conflicts
0x69a491cf…abd7
0xa6afd3…d132
6 touches
3 conflicts
0x5f72d58f…c445
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 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
6 conflicts on slot 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity