← previous blocknext block →recent activity
Analyzing
Block #88,355,354
34 transactions · 24 stateful · 2026-07-17 13:33:27 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
0.88
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #88,355,354 · 34 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w110w011w112w213w315w316w417w520w121w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebac0f82…a49c
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xe2fc9bfe…051c
0x34b655…2a6f
6 touches
3 conflicts
0x8b2e78be…9680
0x34b655…2a6f
6 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 0xebac0f82ec…86a49c
Audit this contract →
← previous block·next block →recent activity