pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,360,819
← previous block
next block →
recent activity
Analyzing
Block #86,360,819
17 transactions · 9 stateful · 2026-07-08 07:13:32 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
#86,360,819
· 17 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execute
#2
updatePrices
#3
0x42bbae7a
#4
executeBatch
#5
batchUpdate
#6
forward
#7
updateDataFeedsValuesPartial
#8
execOrders
#9
0x056a7e…7e68
#10
setData
#11
0x5d29ee…3338
#12
0x3e5119…c068
#13
0x2566a7…0e9c
#14
0xbcda64…678a
#15
withdraw
#16
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
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x293ac8c3…4368
0x188d58…ea8e
2 touches
0 conflicts
0x293ac8c3…4369
0x188d58…ea8e
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