← previous blocknext block →recent activity
Analyzing
Block #88,353,924
21 transactions · 20 stateful · 2026-07-17 13:23:46 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,353,924 · 21 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
1w02w17w08w19w211w212w313w416w517w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8a7b7791…8d1e
0xd32edf…ff58
5 touches
3 conflicts
0x48315f67…c1a6
0x34b655…2a6f
4 touches
1 conflict
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0x5ef12531…ed85
0x34b655…2a6f
4 touches
1 conflict
0xab4aea39…fcaa
0x34b655…2a6f
4 touches
1 conflict
0xbbee202a…8912
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