pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,504,054
← previous block
next block →
recent activity
Analyzing
Block #86,504,054
13 transactions · 10 stateful · 2026-07-08 23:10:47 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,504,054
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
transfer
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
0x6a4ed96f
#8
setData
#9
0xa61c89…0863
#10
0xcc8c2a…9bee
#11
execOrders
#12
0xc7e3ec2c
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
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x02c4bb0f…f2c8
0x34b655…2a6f
2 touches
0 conflicts
0x089552b1…a1cd
0x34b655…2a6f
2 touches
0 conflicts
0x0da39371…1ecd
0x34b655…2a6f
2 touches
0 conflicts
0x0e8d6764…52e9
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