← previous blocknext block →recent activity
Analyzing
Block #96,826,230
36 transactions · 34 stateful · 2026-08-17 16:40:43 UTC
Parallelism
56/100
Blocked
65%
Avg conflicts / tx
2.47
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #96,826,230 · 36 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w17w08w09w310w111w412w413w514w619w820w922w228w1229w230w133w1334w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd676e291…3ecf
0x34b655…2a6f
14 touches
21 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
8 touches
6 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 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
21 conflicts on slot 0xd676e29175…2b3ecf
Audit this contract →
← previous block·next block →recent activity