pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,212,298
← previous block
next block →
recent activity
Analyzing
Block #96,212,298
9 transactions · 6 stateful · 2026-08-15 13:12:35 UTC
Parallelism
78
/100
Blocked
50
%
Avg conflicts / tx
0.44
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,212,298
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#3
execFwdPositionOpsV2
· blocks 2
#5
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#2
0x5acec890
#4
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x05896939…9f49
0x34b655…2a6f
4 touches
1 conflict
0x859fe39d…effa
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x16838830…6ab2
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x722c3231…51e7
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0x66bdb4c268…a97ea6
Audit this contract →
← previous block
·
next block →
recent activity