pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,297,256
← previous block
next block →
recent activity
Analyzing
Block #96,297,256
9 transactions · 8 stateful · 2026-08-15 20:19:54 UTC
Parallelism
56
/100
Blocked
38
%
Avg conflicts / tx
0.67
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,297,256
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5acec890
#3
execFwdPositionOpsV2
· blocks 3
#6
forward
#8
setData
#4
execFwdPositionOpsV2
· blocks 2
#5
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x695f29dd…0c4b
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x8a073405…7cc4
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0xb37dfb6b…268f
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
6 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity