pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,525,474
← previous block
next block →
recent activity
Analyzing
Block #102,525,474
16 transactions · 13 stateful · 2026-09-06 17:15:03 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
#102,525,474
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xa96df62f
#2
execOrders
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
execOrders
#6
0x5acec890
#7
0x5acec890
#8
0x5acec890
#9
0x59558d29
#10
execPerpOps
#11
execPerpOps
#12
setData
#13
execFwdPositionOpsV2
#14
transfer
#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
0x00f6c4dd…22e3
0x34b655…2a6f
2 touches
0 conflicts
0x21adef83…f2b7
0x34b655…2a6f
2 touches
0 conflicts
0x23d03847…102d
0x34b655…2a6f
2 touches
0 conflicts
0x29dbeafe…6ff7
0x34b655…2a6f
2 touches
0 conflicts
0x3bd22e6a…e22c
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