pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,809,709
← previous block
next block →
recent activity
Analyzing
Block #94,809,709
9 transactions · 7 stateful · 2026-08-10 15:21:50 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,809,709
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
repayWithCollateral
#5
execFwdPositionOps
· blocks 1
#7
0x6a79ed06
#8
setData
#6
execFwdPositionOps
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
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0xf60062ab…f98c
0x34b655…2a6f
4 touches
1 conflict
0xf60062ab…f98d
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb4ad3e17…76f4
0x34b655…2a6f
4 touches
1 conflict
0x6cefa2d8…d0d8
0x34b655…2a6f
2 touches
0 conflicts
0x72b612a0…0542
0x34b655…2a6f
2 touches
0 conflicts
0xb9266685…8b1d
0x34b655…2a6f
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
0x734ee32053…cecaae
Audit this contract →
← previous block
·
next block →
recent activity