pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#103,210,112
← previous block
next block →
recent activity
Analyzing
Block #103,210,112
16 transactions · 13 stateful · 2026-09-09 02:49:02 UTC
Parallelism
88
/100
Blocked
8
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#103,210,112
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6aa0c921
#2
0x5acec890
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
redeemDelegations
#7
0xab083028
· blocks 1
#9
execOrders
#10
0x5acec890
#11
0x59558d29
#12
setData
#13
0x3f5c179b
#14
0xed82b078
#15
execFwdPositionOpsV2
#8
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x0990ecee…b4f1
0x34b655…2a6f
2 touches
0 conflicts
0x0e4c2ecd…9581
0x34b655…2a6f
2 touches
0 conflicts
0x2555be96…69db
0x34b655…2a6f
2 touches
0 conflicts
0x2905ed39…1865
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0xaad6be10ae…2c0801
Audit this contract →
← previous block
·
next block →
recent activity