← previous blocknext block →recent activity
Analyzing
Block #87,730,292
14 transactions · 14 stateful · 2026-07-14 15:51:56 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,730,292 · 14 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
2w03w14w25w36w47w18w212w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4de6652…13f4
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x44beb9ca…2366
0x34b655…2a6f
6 touches
3 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x58620f29…db5a
0x34b655…2a6f
6 touches
3 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
5 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
10 conflicts on slot 0xc4de665222…6513f4
Audit this contract →
← previous block·next block →recent activity