pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,309,124
← previous block
next block →
recent activity
Analyzing
Block #96,309,124
7 transactions · 6 stateful · 2026-08-15 21:19:35 UTC
Parallelism
71
/100
Blocked
33
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,309,124
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#4
execFwdPositionOpsV2
#5
updateDataFeedsValuesPartial
#6
setData
#2
0x5acec890
#3
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73670e81…2813
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0229d719…b69e
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x1a86a19b…b4e8
0x34b655…2a6f
2 touches
0 conflicts
0x2b896002…ad21
0x34b655…2a6f
2 touches
0 conflicts
0x2ffa0115…ed47
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
0x73670e81ae…572813
Audit this contract →
← previous block
·
next block →
recent activity