pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,973,688
← previous block
next block →
recent activity
Analyzing
Block #95,973,688
9 transactions · 7 stateful · 2026-08-14 17:12:15 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,973,688
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
_makeSwaps
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
· blocks 1
#7
setData
#8
0xdf2b43…6ed4
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0xf8a748aa…446a
0x34b655…2a6f
4 touches
1 conflict
0x78eb0de5…1db2
0x01bff4…1071
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0000
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…0001
0x2b37ef…0bdc
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
0x6d1b72eefe…416b78
Audit this contract →
← previous block
·
next block →
recent activity