← previous blocknext block →recent activity
Analyzing
Block #88,138,483
24 transactions · 22 stateful · 2026-07-16 13:22:15 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,138,483 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w211w212w215w316w418w319w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25ff7717…d4af
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9465204c…bf37
0x34b655…2a6f
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x42e08579…09bb
0x34b655…2a6f
6 touches
3 conflicts
0xda5c5025…caae
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xdff2c185…0d6f
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: Perpl
6 conflicts on slot 0x25ff77178c…2ad4af
Audit this contract →
← previous block·next block →recent activity