← previous blocknext block →recent activity
Analyzing
Block #88,079,162
22 transactions · 21 stateful · 2026-07-16 06:45:25 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,079,162 · 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
2w04w15w26w39w012w413w114w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xb748f057…8b45
0x40c49f…2af0
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x76d1e78d…7877
0x40c49f…2af0
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0x103be197…826c
0xa6afd3…d132
6 touches
3 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity