← previous blocknext block →recent activity
Analyzing
Block #88,184,096
16 transactions · 15 stateful · 2026-07-16 18:27:59 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,184,096 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w07w19w212w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf86f15cd…38af
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x44fb0f8a…b7c3
0x34b655…2a6f
4 touches
1 conflict
0x44fb0f8a…b7c4
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
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
6 conflicts on slot 0xf86f15cdfb…b938af
Audit this contract →
← previous block·next block →recent activity