← previous blocknext block →recent activity
Analyzing
Block #88,358,573
44 transactions · 26 stateful · 2026-07-17 13:55:16 UTC
Parallelism
89/100
Blocked
38%
Avg conflicts / tx
0.34
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,358,573 · 44 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
1w017w125w029w031w132w233w135w336w237w438w241w342w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00ddbbf2…4588
0x34b655…2a6f
8 touches
6 conflicts
0xad0c145d…72b3
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xda46a376…f6a6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x00ddbbf292…ff4588
Audit this contract →
← previous block·next block →recent activity