pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,567,994
← previous block
next block →
recent activity
Analyzing
Block #95,567,994
11 transactions · 9 stateful · 2026-08-13 07:10:19 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,567,994
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
withdraw
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
0x6a7d6e53
#9
setData
#10
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0x5ec39b23…4581
0x34b655…2a6f
4 touches
1 conflict
0x73b11165…aaea
0x34b655…2a6f
4 touches
1 conflict
0xe21234e7…bded
0x34b655…2a6f
4 touches
1 conflict
0x0d210a18…f399
0x34b655…2a6f
2 touches
0 conflicts
0x18ac919c…d7c5
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x344bc09a…942f
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
0xf85bdc12e0…265dff
Audit this contract →
← previous block
·
next block →
recent activity