pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,865,808
← previous block
next block →
recent activity
Analyzing
Block #92,865,808
12 transactions · 12 stateful · 2026-08-03 20:06:56 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
#92,865,808
· 12 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execFwdPositionOps
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
0x3f5c179b
#5
execFwdPositionOps
#6
execOrders
#7
0x6a70f557
#8
setData
#9
execOrders
#10
0x59558d29
#11
0xc7e3ec2c
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x03a77bc8…a8e4
0x34b655…2a6f
2 touches
0 conflicts
0x05b6db4e…56b6
0x34b655…2a6f
2 touches
0 conflicts
0x0b1ccf85…4ace
0x34b655…2a6f
2 touches
0 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x14caa51c…cabc
0x34b655…2a6f
2 touches
0 conflicts
0x16b085aa…2e7d
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