pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,149,983
← previous block
next block →
recent activity
Analyzing
Block #96,149,983
9 transactions · 8 stateful · 2026-08-15 07:59:11 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,149,983
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x5acec890
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
setData
#8
0x61d59c2d
#2
0x9025acd4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fa57bfc…5a4c
0xef4f3d…7777
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1e737223…2278
0x34b655…2a6f
2 touches
0 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
2 touches
0 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
2 touches
0 conflicts
0x949fc5d9…55f3
0x34b655…2a6f
2 touches
0 conflicts
0xab981df1…2941
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:
0xef4f3dc1…a97777
1 conflict on slot
0x0fa57bfcee…f25a4c
Audit this contract →
← previous block
·
next block →
recent activity