← previous blocknext block →recent activity
Analyzing
Block #88,354,704
14 transactions · 14 stateful · 2026-07-17 13:29:05 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,354,704 · 14 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
6w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x2fdfa032…139c
0x34b655…2a6f
2 touches
0 conflicts
0x7fe97198…79ab
0x34b655…2a6f
2 touches
0 conflicts
0x953517cb…cdec
0x34b655…2a6f
2 touches
0 conflicts
0xd064a456…b881
0x34b655…2a6f
2 touches
0 conflicts
0xd379a368…fea4
0x34b655…2a6f
2 touches
0 conflicts
0xd7668c61…55f8
0x34b655…2a6f
2 touches
0 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity