pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,050,993
← previous block
next block →
recent activity
Analyzing
Block #102,050,993
10 transactions · 10 stateful · 2026-09-05 01:10:16 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
#102,050,993
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x59558d29
#4
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
#7
setData
#8
execFwdPositionOpsV2
#9
forward
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x641aed07…bcb9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x1a30dc9e…7931
0x34b655…2a6f
2 touches
0 conflicts
0x1dca9477…4826
0x34b655…2a6f
2 touches
0 conflicts
0x232b0b19…d946
0x34b655…2a6f
2 touches
0 conflicts
0x35cfc48b…9674
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
0x641aed075a…00bcb9
Audit this contract →
← previous block
·
next block →
recent activity