← previous blocknext block →recent activity
Analyzing
Block #88,360,368
51 transactions · 32 stateful · 2026-07-17 14:07:22 UTC
Parallelism
80/100
Blocked
66%
Avg conflicts / tx
1.37
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #88,360,368 · 51 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w29w310w411w412w513w538w540w641w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x6b9e0b67…af89
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x1bc66ca2…fb4e
0xa6afd3…d132
8 touches
6 conflicts
0x47ac99f8…553b
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9001f549…089d
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity