pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,797,422
← previous block
next block →
recent activity
Analyzing
Block #101,797,422
14 transactions · 13 stateful · 2026-09-04 03:48:21 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,797,422
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrders
· blocks 1
#4
0x5acec890
#5
execOrders
#6
0x59558d29
#7
setData
#8
redeemDelegations
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
updatePriceFeedsIfNecessary
#12
0x57368ddf
#13
execOrders
#3
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c8b719…5f38
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x114f6117…25c0
0x34b655…2a6f
2 touches
0 conflicts
0x269635e7…8a99
0x34b655…2a6f
2 touches
0 conflicts
0x2de87a6a…c195
0x34b655…2a6f
2 touches
0 conflicts
0x3f4b2e63…b468
0x34b655…2a6f
2 touches
0 conflicts
0x49903957…9ab0
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.
The bottleneck
Throughput-killer:
Perpl
1 conflict on slot
0x99c8b71912…425f38
Audit this contract →
← previous block
·
next block →
recent activity