← previous blocknext block →recent activity
Analyzing
Block #95,727,065
11 transactions · 11 stateful · 2026-08-13 20:31:29 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,727,065 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w26w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef1de905…0582
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x16e75abd…f3ad
0x34b655…2a6f
4 touches
1 conflict
0x33f54bd6…9ac3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0xd0391486…43b7
0x34b655…2a6f
4 touches
1 conflict
0xf44bf37e…5d3e
0x065c9d…c394
4 touches
1 conflict
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
3 conflicts on slot 0xef1de9056f…9e0582
Audit this contract →
← previous block·next block →recent activity