pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,105,363
← previous block
next block →
recent activity
Analyzing
Block #99,105,363
13 transactions · 13 stateful · 2026-08-25 17:43:22 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,105,363
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
batchUpdate
#8
0x94defb17
· blocks 1
#10
redeemDelegations
#11
execFwdPositionOpsV2
#12
setData
#9
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bb8193c…0986
0x8964d7…10f8
4 touches
1 conflict
0x8bb8193c…0987
0x8964d7…10f8
4 touches
1 conflict
0x8bb8193c…098a
0x8964d7…10f8
4 touches
1 conflict
0x8bb8193c…098b
0x8964d7…10f8
4 touches
1 conflict
0x8bb8193c…098c
0x8964d7…10f8
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
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:
0x8964d7c9…5b10f8
1 conflict on slot
0x8bb8193c9d…9a0986
Audit this contract →
← previous block
·
next block →
recent activity