pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,163,149
← previous block
next block →
recent activity
Analyzing
Block #85,163,149
12 transactions · 10 stateful · 2026-07-02 18:09:04 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,163,149
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
addLiquidity
· blocks 1
#2
0x5a5d9a99
· blocks 1
#5
0x366fe5db
#6
updateDataFeedsValuesPartial
#7
0x6a46a9b8
#8
setData
#9
execOrders
#10
execOrders
#11
0xc7e3ec2c
#3
0x5a5d9a99
#4
removeLiquidityNATIVE
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0x8f1e8bcc…4662
0x5afd3e…7620
4 touches
1 conflict
0xb70e1a08…fc0e
0x5afd3e…7620
4 touches
1 conflict
0xc08384da…ecb7
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x3378e8b6…20a9
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
0xfaef08b108…f90696
Audit this contract →
← previous block
·
next block →
recent activity