pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,931,632
← previous block
next block →
recent activity
Analyzing
Block #85,931,632
14 transactions · 10 stateful · 2026-07-06 07:28:08 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,931,632
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
addLiquidity
· blocks 1
#4
execPerpOps
#5
execPerpOps
#7
forward
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
0x6a4b5980
#11
setData
#12
0xfe6ca4…409c
#13
execOrders
#6
removeLiquidityNATIVE
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0xe5bb3628…e5e8
0x34b655…2a6f
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x5d399cd5…dfbe
0x5afd3e…7620
2 touches
0 conflicts
0x7bb84687…1706
0x5afd3e…7620
2 touches
0 conflicts
0x9986cd8f…26c7
0x5afd3e…7620
2 touches
0 conflicts
0x9c475805…e1f3
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.
The bottleneck
Throughput-killer:
Liquidity Book Token (LBT)
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity