pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,824,956
← previous block
next block →
recent activity
Analyzing
Block #85,824,956
13 transactions · 11 stateful · 2026-07-05 19:37:27 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,824,956
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
redeemDelegations
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
exec
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
0x36dc1918
· blocks 1
#10
0x6a4ab2ef
#11
setData
#12
0xbed310…5917
#9
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x561da10d…3e86
0x62ab75…c800
4 touches
1 conflict
0x561da10d…3e8d
0x62ab75…c800
4 touches
1 conflict
0x73cb5554…4902
0x754704…b603
4 touches
1 conflict
0x00000000…0005
0x62ab75…c800
4 touches
1 conflict
0x561da10d…3e84
0x62ab75…c800
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
2 touches
0 conflicts
0x4eb758b8…b13b
0x3bd359…433a
2 touches
0 conflicts
0x67d846dd…358c
0x628d67…7777
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:
0x62ab757c…36c800
1 conflict on slot
0x561da10dfd…c63e86
Audit this contract →
← previous block
·
next block →
recent activity