pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,042,778
← previous block
next block →
recent activity
Analyzing
Block #106,042,778
13 transactions · 13 stateful · 2026-09-19 01:12:21 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,042,778
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
0xab083028
#3
execOrders
· blocks 1
#4
updatePrices
#5
0x5acec890
#6
0x5acec890
#7
0x5acec890
#8
updateDataFeedsValuesPartial
#10
0xed82b078
#11
setData
#9
execFwdPositionOpsV2
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
9
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
4 touches
1 conflict
0xc4373871…bc70
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x2b6e2a61…3dae
0x34b655…2a6f
2 touches
0 conflicts
0x3b8d7efd…a779
0x34b655…2a6f
2 touches
0 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
2 touches
0 conflicts
0x742436a7…c4d4
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
0xddd20e3989…a2d524
Audit this contract →
← previous block
·
next block →
recent activity