pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,535,545
← previous block
next block →
recent activity
Analyzing
Block #96,535,545
12 transactions · 9 stateful · 2026-08-16 16:18:41 UTC
Parallelism
83
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,535,545
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x8a369c…5c43
#2
execOrder
· blocks 1
#4
execOrder
#5
redeemDelegations
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
#9
0x94defb17
· blocks 1
#11
setData
#3
execOrder
#10
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f9ea784…18bf
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x4ebcf32a…e39d
0x968279…9342
4 touches
1 conflict
0x4ebcf32a…e39e
0x968279…9342
4 touches
1 conflict
0x4ebcf32a…e3a1
0x968279…9342
4 touches
1 conflict
0x4ebcf32a…e3a2
0x968279…9342
4 touches
1 conflict
0x4ebcf32a…e3a4
0x968279…9342
4 touches
1 conflict
0x8f9ea784…18bc
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0x8f9ea784f5…e118bf
Audit this contract →
← previous block
·
next block →
recent activity