← previous blocknext block →recent activity
Analyzing
Block #96,611,693
27 transactions · 23 stateful · 2026-08-16 22:41:41 UTC
Parallelism
70/100
Blocked
61%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,611,693 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w09w210w411w412w514w418w321w425w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb9834665…e363
0x34b655…2a6f
8 touches
6 conflicts
0x266a2952…28a6
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd996735f…8735
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0b16c8b6…7b05
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 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity