pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,655,055
← previous block
next block →
recent activity
Analyzing
Block #96,655,055
9 transactions · 7 stateful · 2026-08-17 02:19:46 UTC
Parallelism
56
/100
Blocked
43
%
Avg conflicts / tx
0.67
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,655,055
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
#2
0x5acec890
· blocks 3
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#7
setData
#5
execFwdPositionOpsV2
· blocks 2
#6
execFwdPositionOpsV2
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdc1731c…b91a
0x34b655…2a6f
8 touches
6 conflicts
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x1b1451d3…e1f4
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0xc50200b3…a9ed
0x34b655…2a6f
4 touches
1 conflict
0xeff94efd…f7d7
0x34b655…2a6f
4 touches
1 conflict
0xbd75d5bc…78f2
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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
6 conflicts on slot
0xcdc1731c6b…b6b91a
Audit this contract →
← previous block
·
next block →
recent activity