pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,263,387
← previous block
next block →
recent activity
Analyzing
Block #96,263,387
8 transactions · 5 stateful · 2026-08-15 17:29:33 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,263,387
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x80419567
#2
0x5acec890
· blocks 1
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
setData
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0919e62…a2a8
0x34b655…2a6f
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xf73be6c2…3197
0x34b655…2a6f
4 touches
1 conflict
0xa0b89ae7…688a
0x34b655…2a6f
4 touches
1 conflict
0x3036b7d8…6745
0x34b655…2a6f
2 touches
0 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
2 touches
0 conflicts
0x427dec7f…61c6
0x34b655…2a6f
2 touches
0 conflicts
0x67209a5a…ab0e
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
0xd0919e626f…7ea2a8
Audit this contract →
← previous block
·
next block →
recent activity