pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,591,919
← previous block
next block →
recent activity
Analyzing
Block #96,591,919
10 transactions · 8 stateful · 2026-08-16 21:02:13 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,591,919
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execPerpOps
#3
execPerpOps
#4
execOrders
#5
execFwdPositionOpsV2
· blocks 2
#7
updateDataFeedsValuesPartial
#9
setData
#6
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4305f3b…7f3e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0c3210a2…3da8
0x34b655…2a6f
2 touches
0 conflicts
0x0fe510b0…db63
0x34b655…2a6f
2 touches
0 conflicts
0x26607bc2…7fd6
0x34b655…2a6f
2 touches
0 conflicts
0x34933aba…06e4
0x34b655…2a6f
2 touches
0 conflicts
0x34933aba…06e5
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
0xd4305f3b6e…5c7f3e
Audit this contract →
← previous block
·
next block →
recent activity