pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,532,942
← previous block
next block →
recent activity
Analyzing
Block #95,532,942
19 transactions · 17 stateful · 2026-08-13 04:14:01 UTC
Parallelism
95
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,532,942
· 19 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
executeBatch
#5
execFwdPositionOps
#6
CreateMemory
#7
CreateMemory
#8
CreateMemory
#9
CreateMemory
#10
CreateMemory
#11
CreateMemory
#12
CreateMemory
#13
CreateMemory
#14
CreateMemory
#15
CreateMemory
#16
CreateMemory
#17
0x316ba5f2
#18
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
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x2df6f59b…d662
0x34b655…2a6f
2 touches
0 conflicts
0x446c9ed6…c25c
0x34b655…2a6f
2 touches
0 conflicts
0x4adc04e0…113b
0x34b655…2a6f
2 touches
0 conflicts
0x5bdae4ca…5d23
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