← previous blocknext block →recent activity
Analyzing
Block #88,364,158
26 transactions · 21 stateful · 2026-07-17 14:32:49 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,364,158 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w19w010w114w115w217w118w319w321w223w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xad0c145d…72b3
0xa6afd3…d132
6 touches
3 conflicts
0x0c9eb6ea…7c39
0x34b655…2a6f
6 touches
3 conflicts
0x6e1cd42e…1f23
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x61377ba1…0bef
0xa6afd3…d132
4 touches
1 conflict
0x7666ffef…a440
0xa6afd3…d132
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity