pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,593,142
← previous block
next block →
recent activity
Analyzing
Block #95,593,142
14 transactions · 12 stateful · 2026-08-13 09:16:49 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
#95,593,142
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x8263f5d9
#2
claim
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
0xb2d4797b
#9
execFwdPositionOps
#10
execFwdPositionOps
#11
0x6a7d8bf8
#12
setData
#13
0x59558d29
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
0x0e4000ee…afb9
0x34b655…2a6f
2 touches
0 conflicts
0x25191452…d2ed
0x34b655…2a6f
2 touches
0 conflicts
0x77aa49e7…df90
0x34b655…2a6f
2 touches
0 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
2 touches
0 conflicts
0x544ac270…ab6b
0x3bd359…433a
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