pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,716,570
← previous block
next block →
recent activity
Analyzing
Block #95,716,570
9 transactions · 8 stateful · 2026-08-13 19:38:41 UTC
Parallelism
67
/100
Blocked
50
%
Avg conflicts / tx
0.67
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,716,570
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
· blocks 2
#3
updateDataFeedsValuesPartial
#5
0x94defb17
· blocks 2
#8
execFwdPositionOpsV2
#2
execOrder
· blocks 1
#6
0x94defb17
· blocks 1
#4
execFwdPositionOpsV2
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde355cd0…6683
0x968279…9342
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0xd3a52794…9dcc
0x968279…9342
6 touches
3 conflicts
0xd3a52794…9dcd
0x968279…9342
6 touches
3 conflicts
0xd3a52794…9dcf
0x968279…9342
6 touches
3 conflicts
0xde355cd0…667c
0x968279…9342
6 touches
3 conflicts
0xde355cd0…667d
0x968279…9342
6 touches
3 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:
0x96827978…f09342
3 conflicts on slot
0xde355cd0ba…316683
Audit this contract →
← previous block
·
next block →
recent activity