pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,719,601
← previous block
next block →
recent activity
Analyzing
Block #94,719,601
10 transactions · 10 stateful · 2026-08-10 07:47:07 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,719,601
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x5acec890
· blocks 1
#4
0x3f5c179b
#5
execFwdPositionOps
#7
0x6a798272
#8
setData
#9
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a100ac0…96d3
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01dc29d8…bcd2
0x34b655…2a6f
2 touches
0 conflicts
0x111007c2…d736
0x34b655…2a6f
2 touches
0 conflicts
0x16c2ceef…339f
0x34b655…2a6f
2 touches
0 conflicts
0x44f71d02…cc14
0x34b655…2a6f
2 touches
0 conflicts
0x46db28b0…72f6
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
0x5a100ac0d9…2396d3
Audit this contract →
← previous block
·
next block →
recent activity