pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,374,500
← previous block
next block →
recent activity
Analyzing
Block #96,374,500
8 transactions · 7 stateful · 2026-08-16 02:48:24 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,374,500
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
handleOps
#2
updatePrices
#3
execFwdPositionOpsV2
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
· blocks 1
#7
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfeaf7b0…bb92
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x544ac270…ab6b
0x3bd359…433a
2 touches
0 conflicts
0xd2126f3d…f1b6
0x3bd359…433a
2 touches
0 conflicts
0x0b0733bb…5d09
0x3ef3d8…d9ae
2 touches
0 conflicts
0x0b0733bb…5d0a
0x3ef3d8…d9ae
2 touches
0 conflicts
0xd0b8acc5…228d
0x3ef3d8…d9ae
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
0xdfeaf7b0c1…f6bb92
Audit this contract →
← previous block
·
next block →
recent activity