pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,997,544
← previous block
next block →
recent activity
Analyzing
Block #108,997,544
14 transactions · 9 stateful · 2026-09-29 09:13:06 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
#108,997,544
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x5acec890
#2
0x59558d29
#3
updateDataFeedsValuesPartial
#4
execPerpOps
#5
execPerpOps
#6
0x3f5c179b
#7
0xed82b078
#8
0xed82b078
#9
0xed82b078
#10
0xed82b078
#11
execFwdPositionOpsV2
#12
setData
#13
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
0x1032f16c…a9b1
0x34b655…2a6f
2 touches
0 conflicts
0x12e77486…ec2b
0x34b655…2a6f
2 touches
0 conflicts
0x1c414c9c…ccc1
0x34b655…2a6f
2 touches
0 conflicts
0x3b99565b…6441
0x34b655…2a6f
2 touches
0 conflicts
0x3c9b10c1…d791
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