pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,711,335
← previous block
next block →
recent activity
Analyzing
Block #95,711,335
12 transactions · 11 stateful · 2026-08-13 19:12:11 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,711,335
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5acec890
· blocks 2
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0xb2d4797b
#7
relay
#8
forward
#10
setData
#11
execOrders
#6
execFwdPositionOpsV2
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x620b761c…270e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04994ed2…9032
0x34b655…2a6f
2 touches
0 conflicts
0x05d3b9a3…0a91
0x34b655…2a6f
2 touches
0 conflicts
0x11435133…4bf8
0x34b655…2a6f
2 touches
0 conflicts
0x442e26a3…e968
0x34b655…2a6f
2 touches
0 conflicts
0x46db05a5…b8ba
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
0x620b761c50…c2270e
Audit this contract →
← previous block
·
next block →
recent activity