pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,409,844
← previous block
next block →
recent activity
Analyzing
Block #87,409,844
18 transactions · 13 stateful · 2026-07-13 04:08:00 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,409,844
· 18 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
0x3f5c179b
#7
0x57368ddf
#8
execFwdPositionOps
#9
0x6a546518
#10
setData
#11
0xb8024e6e
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
#16
execOrders
#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…0002
0x04fdea…47d7
2 touches
0 conflicts
0x2d1d07e4…eeda
0x34b655…2a6f
2 touches
0 conflicts
0x3c3621c7…3e11
0x34b655…2a6f
2 touches
0 conflicts
0x410b84ab…1dbc
0x34b655…2a6f
2 touches
0 conflicts
0x4cabb80a…46bf
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.
← previous block
·
next block →
recent activity