← previous blocknext block →recent activity
Analyzing
Block #96,604,354
36 transactions · 34 stateful · 2026-08-16 22:04:46 UTC
Parallelism
50/100
Blocked
71%
Avg conflicts / tx
2.39
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #96,604,354 · 36 txs across 18 waves · depth 18
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
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w17w28w29w310w311w412w513w614w715w821w1223w1325w1431w133w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
16 touches
28 conflicts
0x2d651956…12e8
0x34b655…2a6f
14 touches
21 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x5b37bb6b…aaff
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
28 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity