pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,163,902
← previous block
next block →
recent activity
Analyzing
Block #106,163,902
10 transactions · 9 stateful · 2026-09-19 11:21:55 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,163,902
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0xab083028
#3
execOrder
#4
updateDataFeedsValuesPartial
#5
0x59558d29
#6
setData
#7
0x316718…8d0a
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x662d9b98…0f6b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x024b482b…16b0
0x34b655…2a6f
2 touches
0 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
2 touches
0 conflicts
0x12bdab6b…86cb
0x34b655…2a6f
2 touches
0 conflicts
0x41550c5b…a493
0x34b655…2a6f
2 touches
0 conflicts
0x4683bda8…bc84
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
0x045532dd4b…244b7d
Audit this contract →
← previous block
·
next block →
recent activity