pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,204,940
← previous block
next block →
recent activity
Analyzing
Block #95,204,940
16 transactions · 15 stateful · 2026-08-12 00:30:39 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,204,940
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
placeAndExecuteMarketSell
#6
updatePosition
#7
0x6a7bbf27
#8
setData
#9
0x59558d29
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
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
0x300ea4a0…ee47
0x34b655…2a6f
2 touches
0 conflicts
0x3c1ab6b5…4674
0x34b655…2a6f
2 touches
0 conflicts
0x69411fb3…e36d
0x34b655…2a6f
2 touches
0 conflicts
0x6a95ba16…0c9e
0x34b655…2a6f
2 touches
0 conflicts
0x91b0f8ed…6bd6
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