pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,374,621
← previous block
next block →
recent activity
Analyzing
Block #90,374,621
10 transactions · 9 stateful · 2026-07-26 03:03:21 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,374,621
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
0x29eed2d3
· blocks 1
#8
0x6a657971
#9
setData
#7
0x29eed2d3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x5af99590…a658
0x928dc8…8207
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0d488000…3831
0x34b655…2a6f
2 touches
0 conflicts
0x13510de3…1c68
0x34b655…2a6f
2 touches
0 conflicts
0x20fbcaee…bb79
0x34b655…2a6f
2 touches
0 conflicts
0x5a19ef35…dc70
0x34b655…2a6f
2 touches
0 conflicts
0x5e0bf019…75fd
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
0x5311f86450…380984
Audit this contract →
← previous block
·
next block →
recent activity