pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,324,457
← previous block
next block →
recent activity
Analyzing
Block #96,324,457
11 transactions · 10 stateful · 2026-08-15 22:36:43 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,324,457
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
#6
0x3f5c179b
· blocks 1
#8
0x57368ddf
#9
execFwdPositionOpsV2
#10
setData
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9327614…ba36
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0705cc6c…2c40
0x851145…3f07
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
2 touches
0 conflicts
0x2170bea4…4722
0x34b655…2a6f
2 touches
0 conflicts
0x2170bea4…4723
0x34b655…2a6f
2 touches
0 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
2 touches
0 conflicts
0x53ca1284…cb2c
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:
0x851145ea…9f3f07
1 conflict on slot
0xc9327614f6…37ba36
Audit this contract →
← previous block
·
next block →
recent activity