← previous blocknext block →recent activity
Analyzing
Block #88,086,956
18 transactions · 17 stateful · 2026-07-16 07:37:32 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,086,956 · 18 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
2w03w17w08w19w010w111w212w314w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc95f0a1f…6538
0x34b655…2a6f
6 touches
3 conflicts
0x7ed9ab5d…c933
0x34b655…2a6f
4 touches
1 conflict
0x85523e76…ad6c
0x34b655…2a6f
4 touches
1 conflict
0x8dd2ae5f…b8dd
0x34b655…2a6f
4 touches
1 conflict
0x9aea124d…de52
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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity