pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,360,698
← previous block
next block →
recent activity
Analyzing
Block #84,360,698
11 transactions · 8 stateful · 2026-06-29 00:57:00 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,360,698
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
updatePrices
#4
0x3664f7af
#5
execFwdPositionOps
· blocks 1
#7
updateTemporalNumericValuesV1
#8
0x6a41c354
#9
setData
#10
0xf1edd8…7195
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e346a85…e9c5
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000d
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0016
0x1b6862…e19c
2 touches
0 conflicts
0x51f8e55a…1864
0x1b6862…e19c
2 touches
0 conflicts
0x1202acc8…77d0
0x34b655…2a6f
2 touches
0 conflicts
0x23cf86bd…b4a9
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
0x1e346a85f5…1ee9c5
Audit this contract →
← previous block
·
next block →
recent activity