pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,541,155
← previous block
next block →
recent activity
Analyzing
Block #95,541,155
9 transactions · 9 stateful · 2026-08-13 04:55:21 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,541,155
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
0x94defb17
· blocks 2
#7
0x6a7d4eb1
#8
setData
#5
0x94defb17
· blocks 1
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5f175ff…a0bd
0x968279…9342
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x64aaf87f…3b2a
0x968279…9342
6 touches
3 conflicts
0x64aaf87f…3b2b
0x968279…9342
6 touches
3 conflicts
0x64aaf87f…3b2d
0x968279…9342
6 touches
3 conflicts
0xe5f175ff…a0b6
0x968279…9342
6 touches
3 conflicts
0xe5f175ff…a0b7
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
0xe5f175ffa7…06a0bd
Audit this contract →
← previous block
·
next block →
recent activity