pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,867,374
← previous block
next block →
recent activity
Analyzing
Block #90,867,374
10 transactions · 9 stateful · 2026-07-27 20:29:51 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
#90,867,374
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#4
claim
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x6a67c037
#8
setData
#9
0xc7e3ec2c
#5
0xc925b3a5
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0xeea52236…7d3d
0x7b9256…1fb2
4 touches
1 conflict
0x06075577…1330
0x34b655…2a6f
2 touches
0 conflicts
0x6641a47b…d683
0x34b655…2a6f
2 touches
0 conflicts
0x6925548b…81cb
0x34b655…2a6f
2 touches
0 conflicts
0x6925548b…81cc
0x34b655…2a6f
2 touches
0 conflicts
0x734ee320…caae
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:
USDC (USDC)
1 conflict on slot
0xe1f61186c5…67e2f8
Audit this contract →
← previous block
·
next block →
recent activity