pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,901,176
← previous block
next block →
recent activity
Analyzing
Block #95,901,176
8 transactions · 5 stateful · 2026-08-14 11:07:18 UTC
Parallelism
75
/100
Blocked
40
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,901,176
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdraw
#2
execFwdPositionOpsV2
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#7
setData
#3
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3944526b…c457
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0f6aef87…8137
0x34b655…2a6f
2 touches
0 conflicts
0x15086f36…c164
0x34b655…2a6f
2 touches
0 conflicts
0x26cd98c1…9001
0x34b655…2a6f
2 touches
0 conflicts
0x2700d3d0…f370
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0x3944526bf6…9fc457
Audit this contract →
← previous block
·
next block →
recent activity