pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,967,595
← previous block
next block →
recent activity
Analyzing
Block #85,967,595
17 transactions · 16 stateful · 2026-07-06 11:28:05 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
#85,967,595
· 17 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execute_route
#2
execute_route
#3
0x575c0012
#4
0x0c7abd22
#5
execute
#6
exactOutputSingle
#7
execute
#8
exactOutputSingle
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
0x0f6795d9
#12
0x9e76c652
#13
0x0f6795d9
#14
setData
#15
0x39435dac
#16
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
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0xd77e90ec…8c04
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0003
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
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