pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,826,598
← previous block
next block →
recent activity
Analyzing
Block #96,826,598
8 transactions · 6 stateful · 2026-08-17 16:42:34 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,826,598
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOpsV2
· blocks 2
#5
0x3f5c179b
#6
transfer
#7
setData
#3
execFwdPositionOpsV2
· blocks 1
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10fcde4a…83f0
0x34b655…2a6f
4 touches
1 conflict
0xa3d31723…8222
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x309d1b67…0566
0x34b655…2a6f
2 touches
0 conflicts
0x5b37bb6b…aaff
0x34b655…2a6f
2 touches
0 conflicts
0x5b37bb6b…ab00
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
0x10fcde4a76…bd83f0
Audit this contract →
← previous block
·
next block →
recent activity