pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,872,852
← previous block
next block →
recent activity
Analyzing
Block #99,872,852
11 transactions · 11 stateful · 2026-08-28 10:19:43 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,872,852
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
execOrder
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0x59558d29
#7
setData
#8
transferWithAuthorization
#9
execFwdPositionOpsV2
#10
0x6a916137
#2
updatePrices
#5
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21a1d259…eda5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x140145b5…0e95
0x34b655…2a6f
2 touches
0 conflicts
0x2e823c65…b938
0x34b655…2a6f
2 touches
0 conflicts
0x2f4fd493…9935
0x34b655…2a6f
2 touches
0 conflicts
0x40128d8b…37af
0x34b655…2a6f
2 touches
0 conflicts
0x569f2c82…90b1
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
0x21a1d2596d…58eda5
Audit this contract →
← previous block
·
next block →
recent activity