pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,666,169
← previous block
next block →
recent activity
Analyzing
Block #96,666,169
8 transactions · 8 stateful · 2026-08-17 03:15:40 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,666,169
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
execFwdPositionOpsV2
· blocks 2
#7
setData
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9da42530…1c86
0x34b655…2a6f
4 touches
1 conflict
0x48260180…a411
0x34b655…2a6f
4 touches
1 conflict
0xbfbbf561…0976
0x34b655…2a6f
4 touches
1 conflict
0x48260180…a412
0x34b655…2a6f
4 touches
1 conflict
0x7dc9f3ae…116c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x88413c1a…7783
0x34b655…2a6f
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
1 conflict on slot
0x92385428ad…dc6941
Audit this contract →
← previous block
·
next block →
recent activity