pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,733,366
← previous block
next block →
recent activity
Analyzing
Block #87,733,366
18 transactions · 14 stateful · 2026-07-14 16:12:30 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,733,366
· 18 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x50a0b275
#2
0xaf5e395a
#3
____MEV_X____Ga543
#4
0x719d975a
#5
0x0c7abd22
#6
updatePrices
#7
updatePrices
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
execFwdPositionOps
#11
batchUpdate
#12
0x57368ddf
#13
handleOps
#14
execFwdPositionOps
#15
0x6a566066
#16
setData
#17
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0001
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0003
0x019883…2a9a
2 touches
0 conflicts
0x04a63e8d…bf5d
0x0cc9b2…7777
2 touches
0 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…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.
← previous block
·
next block →
recent activity