pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,675,378
← previous block
next block →
recent activity
Analyzing
Block #85,675,378
9 transactions · 7 stateful · 2026-07-05 03:00:09 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,675,378
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x6a49c931
#3
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
permit2TransferAndMulticall
#7
setData
#8
redeemDelegations
#6
execFwdPositionOps
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
0x94f5fc74…a10d
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x1e7e4246…4872
0x34b655…2a6f
4 touches
1 conflict
0xb00a99c0…3cb2
0x34b655…2a6f
4 touches
1 conflict
0xb6994e8b…b528
0x34b655…2a6f
4 touches
1 conflict
0x4bce07ef…8ece
0x34b655…2a6f
2 touches
0 conflicts
0xa563bdb2…1f5c
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.
The bottleneck
Throughput-killer:
Perpl
1 conflict on slot
0x94f5fc7469…10a10d
Audit this contract →
← previous block
·
next block →
recent activity