pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,291,599
← previous block
next block →
recent activity
Analyzing
Block #96,291,599
9 transactions · 8 stateful · 2026-08-15 19:51:27 UTC
Parallelism
67
/100
Blocked
38
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,291,599
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#3
0xa96df62f
#4
0x5acec890
· blocks 2
#6
updateDataFeedsValuesPartial
#8
setData
#2
0xab083028
#5
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff196840…a453
0x34b655…2a6f
6 touches
3 conflicts
0x44331cd1…15b0
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xe9ba215a…1076
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5b
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5c
0x34b655…2a6f
4 touches
1 conflict
0x05286dbb…4517
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot
0xff19684070…f2a453
Audit this contract →
← previous block
·
next block →
recent activity