pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,150,783
← previous block
next block →
recent activity
Analyzing
Block #96,150,783
8 transactions · 7 stateful · 2026-08-15 08:03:12 UTC
Parallelism
50
/100
Blocked
43
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,150,783
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrder
· blocks 3
#4
execFwdPositionOpsV2
#6
setData
#3
execOrder
· blocks 2
#5
execFwdPositionOpsV2
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05896939…9f49
0x34b655…2a6f
2 touches
0 conflicts
0x101726f8…bf51
0x34b655…2a6f
2 touches
0 conflicts
0x1f2deb64…37eb
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c6f
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c70
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
6 conflicts on slot
0x4c18893450…c5158e
Audit this contract →
← previous block
·
next block →
recent activity