pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,317,452
← previous block
next block →
recent activity
Analyzing
Block #99,317,452
9 transactions · 9 stateful · 2026-08-26 11:30:32 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,317,452
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5acec890
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
· blocks 1
#6
0x6a8ececf
#7
setData
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa09be5a…1e79
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1668042d…2ef4
0x34b655…2a6f
2 touches
0 conflicts
0x7f5b2c1d…0e7f
0x34b655…2a6f
2 touches
0 conflicts
0x8b2b7213…4899
0x34b655…2a6f
2 touches
0 conflicts
0x8e99ff06…9eb5
0x34b655…2a6f
2 touches
0 conflicts
0xaba6578d…bd48
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
0xfa09be5aaf…9b1e79
Audit this contract →
← previous block
·
next block →
recent activity