pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,665,143
← previous block
next block →
recent activity
Analyzing
Block #96,665,143
14 transactions · 13 stateful · 2026-08-17 03:10:30 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,665,143
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
poke
#2
poke
#3
poke
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
0x3f5c179b
#10
0x3f5c179b
#11
execFwdPositionOpsV2
#12
execFwdPositionOpsV2
#13
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x03aa8b26…118a
0x34b655…2a6f
2 touches
0 conflicts
0x17fb2c40…8e52
0x34b655…2a6f
2 touches
0 conflicts
0x1a5d321d…a474
0x34b655…2a6f
2 touches
0 conflicts
0x36cf7d70…f333
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.
← previous block
·
next block →
recent activity