pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,276,015
← previous block
next block →
recent activity
Analyzing
Block #96,276,015
9 transactions · 7 stateful · 2026-08-15 18:33:04 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,276,015
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
· blocks 1
#3
execFwdPositionOpsV2
· blocks 1
#4
updatePosition
#6
updateDataFeedsValuesPartial
#7
depositTo
#8
setData
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
0x34b655…2a6f
4 touches
1 conflict
0x9a8b7004…3e0a
0x34b655…2a6f
4 touches
1 conflict
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0xb8ce1c1c…16b5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
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
0x0bd95eb406…f6e562
Audit this contract →
← previous block
·
next block →
recent activity