pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,697,233
← previous block
next block →
recent activity
Analyzing
Block #96,697,233
11 transactions · 10 stateful · 2026-08-17 05:51:54 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,697,233
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#6
execOrders
#7
execFwdPositionOpsV2
· blocks 1
#9
0xed82b078
#10
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x3f2796bf…f0fa
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
2 touches
0 conflicts
0x5c10927c…58e5
0x34b655…2a6f
2 touches
0 conflicts
0x5da59c2b…d7b2
0x34b655…2a6f
2 touches
0 conflicts
0x6bdb9869…7558
0x34b655…2a6f
2 touches
0 conflicts
0x744dc4cc…767f
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity