← previous blocknext block →recent activity
Analyzing
Block #88,355,066
44 transactions · 33 stateful · 2026-07-17 13:31:30 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.39
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #88,355,066 · 44 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w017w018w119w220w321w423w524w628w729w833w136w137w938w1039w1140w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb874a6c…caa0
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xebac0f82…a49c
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xf565ea1f…4245
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xb10a849a…a23f
0xd32edf…ff58
7 touches
6 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 0xfb874a6c9f…bfcaa0
Audit this contract →
← previous block·next block →recent activity