pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,496,390
← previous block
next block →
recent activity
Analyzing
Block #96,496,390
12 transactions · 4 stateful · 2026-08-16 13:01:30 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,496,390
· 12 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x10ae4f…0447
#2
0x6a891d…6d6e
#3
0x9cd5c5…2c92
#4
0x37dcf5…7d15
#5
0x4dbe72…ae80
#6
0x1ef095…cca7
#7
0x5acec890
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
updateDataFeedsValuesPartial
#11
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
0x079bf666…56c4
0x34b655…2a6f
2 touches
0 conflicts
0x09396f14…669f
0x34b655…2a6f
2 touches
0 conflicts
0x1c097b81…0164
0x34b655…2a6f
2 touches
0 conflicts
0x1c097b81…0165
0x34b655…2a6f
2 touches
0 conflicts
0x31519d10…f76b
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