pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,579,933
← previous block
next block →
recent activity
Analyzing
Block #96,579,933
11 transactions · 8 stateful · 2026-08-16 20:01:55 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,579,933
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x0c7abd22
#8
execFwdPositionOpsV2
· blocks 1
#9
execFwdPositionOpsV2
#2
updatePrices
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x16838830…6ab2
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x4a2dd131…efef
0x34b655…2a6f
2 touches
0 conflicts
0x5eac44da…0868
0x34b655…2a6f
2 touches
0 conflicts
0x9c3004b2…5421
0x34b655…2a6f
2 touches
0 conflicts
0xa01f2285…f16f
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
0x24b08f9c98…6ae594
Audit this contract →
← previous block
·
next block →
recent activity