pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,665,096
← previous block
next block →
recent activity
Analyzing
Block #98,665,096
9 transactions · 8 stateful · 2026-08-24 04:35:47 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
#98,665,096
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateTemporalNumericValuesV1
#7
0x6a8bca9a
#8
setData
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0e974c4…b84d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x1867b653…e61b
0x34b655…2a6f
2 touches
0 conflicts
0x18b65823…058d
0x34b655…2a6f
2 touches
0 conflicts
0x3013c848…bd3c
0x34b655…2a6f
2 touches
0 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
2 touches
0 conflicts
0x73a33694…9d5d
0x34b655…2a6f
2 touches
0 conflicts
0x7caa7672…a023
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
0xb0e974c47d…53b84d
Audit this contract →
← previous block
·
next block →
recent activity