pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,689,793
← previous block
next block →
recent activity
Analyzing
Block #87,689,793
10 transactions · 8 stateful · 2026-07-14 11:20:40 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,689,793
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
updateTemporalNumericValuesV1
#6
0x6a561bff
#7
setData
#8
0x34653439
#9
0x3e0334…95a8
#4
execFwdPositionOps
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
0xda46a376…f6a6
0x34b655…2a6f
4 touches
1 conflict
0xca2926e0…61b5
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x20067ecb…0e41
0x34b655…2a6f
2 touches
0 conflicts
0x272e5bd6…252d
0x34b655…2a6f
2 touches
0 conflicts
0x28370d24…4a0f
0x34b655…2a6f
2 touches
0 conflicts
0x28370d24…4a10
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
0xda46a376d7…59f6a6
Audit this contract →
← previous block
·
next block →
recent activity