pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,744,009
← previous block
next block →
recent activity
Analyzing
Block #95,744,009
8 transactions · 7 stateful · 2026-08-13 21:56:42 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,744,009
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xeb282f7f
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
· blocks 1
#7
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f6bc8db…0519
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xcba9f8ce…88f5
0x1efe02…37d6
2 touches
0 conflicts
0x49a886f9…b069
0x754704…b603
2 touches
0 conflicts
0x6bf1a5ae…1f9a
0x754704…b603
2 touches
0 conflicts
0xc96ef8cc…ff2e
0x754704…b603
2 touches
0 conflicts
0x6366da4a…bc10
0xea1b8e…c5ec
2 touches
0 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:
Perpl
1 conflict on slot
0x5f6bc8db1a…f60519
Audit this contract →
← previous block
·
next block →
recent activity