pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,523,079
← previous block
next block →
recent activity
Analyzing
Block #85,523,079
10 transactions · 9 stateful · 2026-07-04 10:06:03 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,523,079
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
removeLiquidityNATIVE
#3
0x0f6795d9
· blocks 1
#4
forward
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#9
0xc7e3ec2c
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x830b63a6…8105
0x34b655…2a6f
4 touches
1 conflict
0xd2862d04…388c
0x34b655…2a6f
4 touches
1 conflict
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x1106cf0b…7986
0x34b655…2a6f
4 touches
1 conflict
0xe7b3c498…7d6e
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x4039b31f…0f4a
0x754704…b603
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.
The bottleneck
Throughput-killer:
Perpl
1 conflict on slot
0x737acb7813…fafce8
Audit this contract →
← previous block
·
next block →
recent activity