pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,121,554
← previous block
next block →
recent activity
Analyzing
Block #96,121,554
10 transactions · 9 stateful · 2026-08-15 05:36:07 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,121,554
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
· blocks 1
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x57368ddf
#9
setData
#7
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xfb54d14d…1ecf
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x05ae5149…f967
0x34b655…2a6f
2 touches
0 conflicts
0x064bb149…79fd
0x34b655…2a6f
2 touches
0 conflicts
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x23253ea8…e0a4
0x34b655…2a6f
2 touches
0 conflicts
0x27f75f20…525c
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
0x6d1b72eefe…416b78
Audit this contract →
← previous block
·
next block →
recent activity