← previous blocknext block →recent activity
Analyzing
Block #88,359,357
22 transactions · 22 stateful · 2026-07-17 14:00:32 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,359,357 · 22 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
1w02w03w14w25w27w08w110w011w112w215w316w217w420w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7dc68577…fbf1
0x34b655…2a6f
6 touches
3 conflicts
0x3eb40fbb…fa8b
0xd32edf…ff58
5 touches
3 conflicts
0x5e8ddd73…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x5c62c3eb…d209
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity