pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,591,656
← previous block
next block →
recent activity
Analyzing
Block #95,591,656
13 transactions · 12 stateful · 2026-08-13 09:09:20 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
#95,591,656
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
0x5acec890
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x222d4ad6
#9
0x94defb17
· blocks 1
#11
0x927825be
#12
0x59558d29
#10
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x288157e9…4495
0x968279…9342
4 touches
1 conflict
0x288157e9…4498
0x968279…9342
4 touches
1 conflict
0x288157e9…4499
0x968279…9342
4 touches
1 conflict
0x288157e9…449a
0x968279…9342
4 touches
1 conflict
0x8ad29028…1d2f
0x968279…9342
4 touches
1 conflict
0x8ad29028…1d30
0x968279…9342
4 touches
1 conflict
0x8ad29028…1d32
0x968279…9342
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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
0x288157e901…384495
Audit this contract →
← previous block
·
next block →
recent activity