pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,442,813
← previous block
next block →
recent activity
Analyzing
Block #98,442,813
15 transactions · 11 stateful · 2026-08-23 09:26:50 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
#98,442,813
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrders
#2
execOrders
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
execOrders
#6
0x59558d29
#7
execPerpOps
#8
0x5acec890
#9
execFwdPositionOpsV2
#10
0x3f5c179b
#11
execFwdPositionOpsV2
#12
setData
#13
execOrders
#14
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
0x02f1066b…9138
0x34b655…2a6f
2 touches
0 conflicts
0x04c65c08…63c2
0x34b655…2a6f
2 touches
0 conflicts
0x1204f20c…3f98
0x34b655…2a6f
2 touches
0 conflicts
0x3a7fb5b5…f0e5
0x34b655…2a6f
2 touches
0 conflicts
0x3c495b3c…4ed9
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