pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,568,958
← previous block
next block →
recent activity
Analyzing
Block #95,568,958
11 transactions · 10 stateful · 2026-08-13 07:15:10 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,568,958
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#6
0x29eed2d3
#7
0x6a7d6f76
#8
setData
#9
0x59558d29
#10
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0a0cecef…4ed0
0x34b655…2a6f
2 touches
0 conflicts
0x0fb9e50c…1a35
0x34b655…2a6f
2 touches
0 conflicts
0x1683d146…5ec2
0x34b655…2a6f
2 touches
0 conflicts
0x37d710c8…45c1
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
0xa998841984…609f45
Audit this contract →
← previous block
·
next block →
recent activity