← previous blocknext block →recent activity
Analyzing
Block #88,137,092
18 transactions · 18 stateful · 2026-07-16 13:12:58 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,137,092 · 18 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
3w04w15w27w08w110w111w212w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
6 touches
3 conflicts
0xfebaf6fc…61b5
0x34b655…2a6f
6 touches
3 conflicts
0xf66a16ae…0da8
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: 0xc1ff9fef…f4b0fc
3 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity